…many subtle bugs from interesting intersections between Rails (I'm looking at you, ActiveSupport) and the various flavors of Ruby. Running the unit tests under Rails helps flush out these odd interactions. For example, we found one problem with subtly incompatible versions of the to_json method floating around during the 2.x versions of ActiveSupport.
Which version of Rails do we run against? Well, if you download the agent source and run the unit tests, you'll see …
- giant robots smashing into other giant robots: She Blinded Me with Ruby Science
- Engine Yard Developer Blog: Announcing the Engine Yard Innovators Awards
- A Fresh Cup: Double Shot #1075
- Mike Perham: 12 Gems of Christmas #3 - thor
- Hobo Blog: 2.0.0.pre8: final prerelease
- Litany Against Fear: Use Jekyll, SCSS, and CoffeeScript without plugins
…diagnostic code I whipped up yesterday to add ActiveRecord callbacks to the development log.
activerecord-callback_notification - This one didn't do quite what I want, but I borrowed some of its code to start from.
Instrument Anything in Rails 3 - A good introduction to ActiveSupport::Notifications.
callback_skipper - Short-circuit things in your unit tests.
- Plataformatec Blog: Extending and customizing 3rd party code
- Giles Bowkett: Node.js Hatred Reveals Significant Dysfunction In The Ruby Culture
- Viget.com Blogs: Using Time Zones with Rails
- giant robots smashing into other giant robots: Giving thanks
- Ruby Inside: The Last Week in Ruby: A Great Ruby Shirt, RSpec Team Changes and a Sneaky Segfault Trick
- RailsTips by John Nunemaker: An Instrumented Library in ~30 Lines
…rails 4.0.0.beta1 . Rails 4 provides updated versions of the ActiveSupport::Notifications libraries, which generate a queue of events containing performance timing information. The latest versions of the Ruby agent subscribe to these event streams, allowing us to integrate more seamlessly into the framework and avoid excessive monkey-patching. The highlights for Rails 4 include strong parameters, turbolinks, and Russion doll caching. See the Rails 4 release notes for …
- Mike Perham: 12 Gems of Christmas #1 - puma
- Transcending Frontiers: Let's Talk About RubyMotion
- The Real Adam: Twitter's optimizations
- Signal vs. Noise: Why I learned to "make things"
- Ruby News: Denial of Service and Unsafe Object Creation Vulnerability in JSON (CVE-2013-0269)
- Litany Against Fear: Use Jekyll, SCSS, and CoffeeScript without plugins
…should. While this might make a lot of sense for libraries that extend the Ruby stdlib (like ActiveSupport ), monkeypatching someone else constant might bite you back later. Overusing monkeypatches might be a serious block when updating your application to newer versions of a big dependency of your project (for example, Rails).
When you monkey patch, you are usually messing with a very internal piece of a component that might be far from it's public API. So, you can't predict …
- has_many :through: Modularized Association Methods in Rails 3.2
- Ruby Inside: The Past 2 Weeks in the World of Ruby: 40 Links to Bring You Up to Speed (January 2012)
- igvita.com: Wait, Chrome DevTools could do THAT?
- Segment7: mechanize 2.0
- Signal vs. Noise: Behind the scenes: A/B testing part 2: How we test
- RubyLearning Blog: Interview: Michael Hartl, author of the Ruby on Rails Tutorial (railstutorial.org)
…check for the development environment appears to be necessary, because Rails uses some of ActiveSupport's test-related classes in the development environment!
Option 2 - Use "edge" Rails or one of the relevant "stable" branches of Rails # Gemfile gem "rails", git: "git://github.com/rails/rails.git", branch: "3-2-stable" group :test do gem "mocha", :require => false end
# test/test_helper.rb require …
- Blog - James Mead: Using Mocha with Rails 3 and Test::Unit
- A Fresh Cup: Double Shot #1011
- Medium eXposure: Getting Rails 2.3.3 and Mocha >=0.9.6 to play nice with Test::Unit and Shoulda
- Viget.com Blogs: Testing Google Analytics with PhantomJS
- Gears Within Gears: Mocking in ISpec: A first pass
- Labnotes: Rounded Corners 372 - Czechsum Function
…to this.
RailsCasts: Notifications in Rails 3
Digging Deep with ActiveSupport Notifications
Instrument Anything in Rails 3
On Notifications, Log Subscribers and Bringing Sanity to Rails Logs
Fin
Go forth and instrument all the things!
- Giles Bowkett: The "private" Keyword Disregards Professional Courtesy
- carpeaqua by Justin Williams: Issues With Achieving Auto Layout Zen
- Engine Yard Developer Blog: Instrumenting excon
- paperplanes: A Plea for Client Library Instrumentation
…that is all over Google search. Here's the equivalent code before I extracted to a ActiveSupport::Concern module
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 class Foo < ActiveRecord :: Base after_commit :clear_id_cache # class method def self . lookup_by_id (id) Rails .cache.fetch( " Foo:id: #{ id } " ) do where( :id => id).first …
- Riding Rails - home: Rails 3.2.0.rc2 has been released!
- paperplanes: A Plea for Client Library Instrumentation
- Simone Carletti's Blog: Inside Ruby on Rails: Serializing Ruby objects with JSON
- Ruby on Rails Development: Ruby on Rails Deprecations Part 1: ActionController
- Codeulate.: Let's read some Rails code: OrderedOptions
- for i in infinity: Introducing MooModel: A Javascript Framework
…rails allows arbitrary code execution on an affected server. The vulnerable code is in rails's ActiveSupport library. Though the current versions of Chef server use Merb instead of rails, Merb uses an ActiveSupport fork called extlib that includes the same vulnerability to provide many of the same features as ActiveSupport. According to the currently available information about the vulnerability, there are several additional conditions that must be satisfied for the vulnerability …
- Opscode Blog: Chef 10.18.0 Released!
- Engine Yard Developer Blog: Rails 3 Beta is Out — A Retrospective
- has_many :bugs, :through => :rails: Introducing Cramp
- AdaRuby: Rails 3 Beta Ready with Merb Goodness
- RubyLearning Blog: Ruby Metaprogramming New Batch Announced
- giant robots smashing into other giant robots: Test Time Bombs
…that, on the surface, make it easier for Rails to extend the Ruby language via ActiveSupport. I think that's too shallow of a reading. The new tools in Ruby 2.0 (excepting the highly-controversial refinements) make it easier to cleanly add functionality to Ruby's core objects and library. Reducing the cost of extending the core make it possible for more libraries and applications to judiciously make high-leverage additions to the lower levels of Ruby. That seems like a pretty …
- Justin Leitgeb: Moving beyond mixins
- Headius: Refining Ruby
- Matthew Bass: RubyConf 2012 recap
- Phusion Corporate Blog: Phusion Passenger 4.0 supports JRuby, Rubinius
- RubyLearning Blog: A "FREE" Online Course: Programming for the Web with Ruby
- Brightbox Ruby Blog: Passenger 3.0.17 and NGINX 1.2.3 packages for Ubuntu
…could start by adding optional instrumentation based on AS::Notifications. That'd ensure that ActiveSupport itself doesn't turn into a direct dependency. I'd love to see the notifications bit being extracted into a separate library that's easier to integrate than pulling in the entire ActiveSupport ball of mud.
Node.js has EventEmitters , which are similar to AS::Notifications, and they lend themselves quite nicely for this purpose.
I've dabbled with …
- Labnotes: 2011 is year of the Server-Side JavaScript
- JJinuxLand: HTML5 Dev Conf
- Global Nerdy: Two Great Node Books at One Great Price: The Node Beginner Book and Hands-On Node.js
- Trevor Turk: Links for 5-17-11
- Merbist: Data safety and GIL removal
- High Scalability: LinkedIn Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster