chrisbloom7

# frozen_string_literal: true

# Basic implementation of a websocket connector for Slack using the slack-ruby-client gem
# 
# Run this rake task in a virtual container that is set to automatically restart on failure; this
# will help deal with disconnects from Slack since socket URLs are temporary.
# https://api.slack.com/apis/connections/socket-implement#disconnect
#
# This rake task can be called in multiple virtual containers to help with resilliancy and rolling restarts
# https://api.slack.com/apis/connections/socket-implement#connections

chrisbloom7

<?php
function longest_common_substring($words)
{
  $words = array_map('strtolower', array_map('trim', $words));
  $sort_by_strlen = create_function('$a, $b', 'if (strlen($a) == strlen($b)) { return strcmp($a, $b); } return (strlen($a) < strlen($b)) ? -1 : 1;');
  usort($words, $sort_by_strlen);
  // We have to assume that each string has something in common with the first
  // string (post sort), we just need to figure out what the longest common
  // string is. If any string DOES NOT have something in common with the first
  // string, return false.

chrisbloom7

Note that this validation runs both after the file is uploaded and after CarrierWave has processed the image. If your base uploader includes a filter to resize the image then the validation will be run against the resized image, not the original one that was uploaded. If this causes a problem for you, then you should avoid using a resizing filter on the base uploader and put any specific size requirements in a version instead.

So instead of this:

require 'carrierwave/processing/mini_magick'

chrisbloom7

# Generate a password that is 8 - 20 characters in length, and which contains at least one number and one special character
# Requires Ruby >= 1.9
def random_password
  specials = ((32..47).to_a + (58..64).to_a + (91..96).to_a + (123..126).to_a).pack('U*').chars.to_a
  numbers  = (0..9).to_a
  alpha    = ('a'..'z').to_a + ('A'..'Z').to_a
  %w{i I l L 1 O o 0}.each{ |ambiguous_character| 
    alpha.delete ambiguous_character 
  }
  characters = (alpha + specials + numbers)

chrisbloom7

<?php
/**
 * In your Apache conf file, set the following to enable XSendfile:
 * 
  <Directory "/">
    # This should be handled by the XSendFile module, but a bug in 0.11.1 prevented it from being set properly.
    EnableSendfile on
  
    XSendFile on

chrisbloom7

I've found a bug that is specific to the following scenario:

• Using MySQL
• Using a longblob column type
• Using a serialized attribute
• Using paper_trail gem
• Serialized field contains unicode character

Under those conditions, after saving changes to the serialized field, record#changed? still reports true, and record#changes contains an entry for the serialized field where both the before and after elements are identical. Calling record#reload clears the changes and loads the record with the changed value. If paper_trail is removed from the scenario, the ActiveModel attribute mutation tracking works as expected.

chrisbloom7

chrisbloom7

colors = ["red"]   #=> ["red"]
colors_2 = colors  #=> ["red"]
colors_2 << "blue" #=> ["red", "blue"]
colors             #=> ["red", "blue"]

def add_white (original_colors)
  original_colors << "white"
end

add_white colors   #=> ["red", "blue", "white"]

chrisbloom7

class MySingletonClass
  include Singleton

  attr_reader :client

  def initialize
    @client = Service::We::Only::Ever::Need::One::Connection::To.new(SERVICE_URL)
  end
end

chrisbloom7

# app/models/change.rb
class Change < ActiveRecord::Base
  belongs_to :changeset, inverse_of: :changed_fields
  validates :changeset, presence: true, associated: true
  validates :field, presence: true, uniqueness: {scope: :changeset_id}, inclusion: { in: :field_enum }

  def field_enum
    if changeset.try(:model).present?
      changeset.model_attributes
    else