-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOError not opened for reading #51
Comments
+1 |
While #52 says that 0.2.5 should improve Rails 4 pre-release support, I am still seeing the above issue with this newer |
Can you please paste your Gemfile. Thanks. |
@dejan Here's a gist: https://gist.github.com/shanesveller/80a010c63b58c3f2bc7f This is ultra low-priority for me, I'm only a hobby programmer experimenting with bumping a project app to Rails 4. I appreciate you taking the time to look at it whenever you like. |
+1 |
Not sure if this will help, but quick research into this error shows that app_request.events contains 'process_action.action_controller' event which references (via payload[:request]) the current Rack::Request. Calling to_json on Rack::Request object fails for me, probably because it contains references to IO objects (like STDERR). Tested on ruby 2.0, Rails 4 RC1. |
@shanesveller thank you very much for the Gemfile. It helped me recreate the issue and fix it. The newrelic_rpm gem set the payload[:request] that contained some closed IO as @zzemia discovered. |
Fix is in meta_request 0.2.6. |
Works for me. Thanks! |
Suddenly I get an IOError in my development machine for every request.
It occures in activesupport-4.0.0.beta1/lib/active_support/json/encoding.rb, line 256:
which is triggered from meta_request-0.2.3/lib/meta_request/middlewares/app_request_handler.rb, line 21:
It seems to be the exact same issue as rollbar/rollbar-gem#32 and already appeared with meta_request in markevans/dragonfly#18.
The text was updated successfully, but these errors were encountered: