{"issue":{"created_at":"2011-11-29T22:54:16Z","state":"open","updated_at":"2011-11-30T15:10:45Z","comments":3,"user":{"gravatar_id":"39645efbd222c6c512f7ba0d9abadbbf","id":386473,"url":"https://api.github.com/users/devigned","avatar_url":"https://secure.gravatar.com/avatar/39645efbd222c6c512f7ba0d9abadbbf?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"devigned"},"body":"To get the specs passing within 3.1.1 I needed to added in the yajl engine, and a require to ActiveSupport core extensions to fix issue: https://github.com/CompanyBook/massive_record/issues/42. There was also an issue with the notifier dying in the database cleaner.\r\n\r\nThe specs are passing with the changes.\r\n\r\n\r\nComment:\r\nFixed the issues with the spec passing for 3.1. Added in yajl to the gemspec. Updated the database cleaner to make sure there is a notifier for the instrumenter when data needs to be cleaned up.","assignee":null,"pull_request":{"patch_url":"https://github.com/CompanyBook/massive_record/pull/80.patch","html_url":"https://github.com/CompanyBook/massive_record/pull/80","diff_url":"https://github.com/CompanyBook/massive_record/pull/80.diff"},"id":2394747,"number":80,"labels":[],"title":"Fixed issues when moving to rails 3.1","html_url":"https://github.com/CompanyBook/massive_record/issues/80","closed_at":null,"url":"https://api.github.com/repos/CompanyBook/massive_record/issues/80","milestone":null},"action":"created","comment":{"created_at":"2011-11-30T15:10:45Z","updated_at":"2011-11-30T15:10:45Z","user":{"gravatar_id":"39645efbd222c6c512f7ba0d9abadbbf","id":386473,"url":"https://api.github.com/users/devigned","avatar_url":"https://secure.gravatar.com/avatar/39645efbd222c6c512f7ba0d9abadbbf?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"devigned"},"body":"I have not verified backward compatibility with Rails 3.0.X. I'm betting it doesn't currently.","id":2960815,"url":"https://api.github.com/repos/CompanyBook/massive_record/issues/comments/2960815"}}