{"issue":{"pull_request":{"diff_url":"https://github.com/datamapper/dm-rails/pull/28.diff","html_url":"https://github.com/datamapper/dm-rails/pull/28","patch_url":"https://github.com/datamapper/dm-rails/pull/28.patch"},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/f855324f298eb7708e39ea117477cbd5?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"f855324f298eb7708e39ea117477cbd5","url":"https://api.github.com/users/d11wtq","login":"d11wtq","id":37948},"milestone":null,"assignee":null,"updated_at":"2011-11-12T07:40:02Z","labels":[],"comments":3,"closed_at":"2011-11-12T07:39:52Z","url":"https://api.github.com/repos/datamapper/dm-rails/issues/28","body":"This fixes the session store in Rails 3.1, as reported by this user:\r\n\r\nhttp://stackoverflow.com/questions/7831431/sessions-with-datamapper-dont-work-due-to-an-argumenterror?utm_source=twitterfeed&utm_medium=twitter\r\n\r\nWe ran into the same issue with our own custom session store and I never thought to check if DM's was affected.  Rails 3.1 passed extra options parameters into some methods in the session store, which cause an ArgumentError.\r\n","html_url":"https://github.com/datamapper/dm-rails/issues/28","title":"Fix incomaptibility with number of arguments in Rails 3.1 vs 3.0","number":28,"id":2002152,"created_at":"2011-10-20T07:22:42Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/7c92608db4acf7a44337670eff6ce5bc?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"7c92608db4acf7a44337670eff6ce5bc","url":"https://api.github.com/users/dkubb","login":"dkubb","id":133},"updated_at":"2011-11-12T07:40:02Z","url":"https://api.github.com/repos/datamapper/dm-rails/issues/comments/2716465","body":"Thanks for the pull request!","id":2716465,"created_at":"2011-11-12T07:40:02Z"}}