revans

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

revans

config.middleware.use RoutesReloader

revans

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

revans

class Api::UploadsController < ApiController

  def create
    @upload = Upload.new(upload_params)
  ensure
    clean_tempfile
  end

  private

revans

  class RouteRecognizer
    attr_reader :paths
    
    # To use this inside your app, call:
    # `RouteRecognizer.new.initial_path_segments`
    # This returns an array, e.g.: ['assets','blog','team','faq','users']

    INITIAL_SEGMENT_REGEX = %r{^\/([^\/\(:]+)}

    def initialize

revans

require 'md5'

class Chargify::HooksController < ApplicationController
	protect_from_forgery :except => :dispatch
	before_filter :verify, :only => :dispatch

	EVENTS = %w[ test signup_success signup_failure renewal_success renewal_failure payment_success payment_failure billing_date_change subscription_state_change subscription_product_change ].freeze

	def dispatch
		event = params[:event]

revans

# MODEL

class Case < ActiveRecord::Base
  include Eventable
  
  has_many :tasks

  concerning :Assignment do
    def assign_to(new_owner:, details:)
      transaction do

revans

module ObjectDiagnostics
  extend self

  #This is handy when you want to determine what types of objects are contributing to memory bloat  
  #returns the change in object counts since the last time this method was called
  def change_in_object_counts
    
    #this will start all counts at 0 for the initial run
    @previous_counts ||= Hash.new(0)

revans

# /etc/init/project-web-reload.conf

pre-start script
  initctl restart project-web
  sleep 15
end script

exec /usr/local/rvm/bin/default_bluepill restart

revans

# coding: utf-8
require 'sinatra'
set server: 'thin', connections: []

get '/' do
  halt erb(:login) unless params[:user]
  erb :chat, locals: { user: params[:user].gsub(/\W/, '') }
end

get '/stream', provides: 'text/event-stream' do