-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Sentry errors out with - undefined method `[]' for nil:NilClass #932
Comments
I am seeing so many of these errors. I am a regular Bugsnag user for most of my projects, but wanted to give Sentry a try, but it looks like this is not a production ready service. |
Have this too. Seems to come from this https://github.com/getsentry/raven-ruby/compare/v2.11.3..v2.12.0#diff-c6aec131e87f11962bba5dcfa61a07d9R82-R86 |
It can be easily reproduced by an offline network. sentry-raven version: 2.12.0 Reproduce steps:
The error logs for SentryJob:
|
This is a very big problem @nateberkopec @HazAT you need to pull this release and/or issue a bugfix release as soon as you can. Redis servers/clusters will take a while to keel over due (memory bloat, out of memory, swap to disk, bye bye) to this but they eventually will and in our experience (staging and production) that seems to correlate with normal exception volume so it's easy to accidentally dismiss as a false negative (the Sentry Exception from SentryWorker for |
Hello! :) After release with update sentry-raven from 2.9 to 2.12 SentryJob sent fails to our sentry account. Our site was crashed with very large response time from our services which also uses same redis for another reasons. We tried run Why we not found this issue #932 before release? I don't know :( Moral: |
Hey, really sorry about that, I will fix this first thing tomorrow morning. |
|
I am still experiencing this exception with 2.12.2, because I have this custom block: config.should_capture = Proc.new { |e| !e.message['Broken pipe'] } It looks like the message property was actually removed in #931 but I'm surprised this wasn't advertised as a breaking change, the changelog entry doesn't sound worrying. I tried to find the new recommended way to do this but didn't find any example. The property is still in the class so is it normal that it's sometimes |
Environment -
Sentry Config -
Error Message - "undefined method `[]' for nil:NilClass"
Error Stack -
Sidekiq Arguments -
The text was updated successfully, but these errors were encountered: