You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating to sentry-rails4.3.3 from 4.3.1 in our Rails 6.1 app we're seeing an issue starting our Rails server. It looks like we're getting a undefined method debug' for nil:NilClasserror coming from the initializer forBackgroundWorkerwhen it callsconfiguration.logger.debug(LOGGER_PROGNAME)`.
I don't think we have an unusual logger setup to my knowledge, so I'm not sure why this is suddenly causing an issue, and I'm wondering what would have changed between these minor version releases (downgrading back to 4.3.1 fixes the issue) that we might need to account for.
The text was updated successfully, but these errors were encountered:
@brooksco I think this is the same problem as #1368, which could be solved if you move the configs into config/initializers/sentry.rb.
the root cause is that v4.3.3 fixes the sentry-rails' logger assignment, which requires the SDK to be initialized as one of the Rails initializers (this was expected but not required until now). I'll try to add a warning message to hint misplaced configurations.
@st0012 ah got it, I missed that since it was closed (should have checked there first). That fixed my issue. Thanks! Maybe a warning can help the next person who comes along and does what I did.
After updating to
sentry-rails
4.3.3
from4.3.1
in our Rails 6.1 app we're seeing an issue starting our Rails server. It looks like we're getting aundefined method
debug' for nil:NilClasserror coming from the initializer for
BackgroundWorkerwhen it calls
configuration.logger.debug(LOGGER_PROGNAME)`.I don't think we have an unusual logger setup to my knowledge, so I'm not sure why this is suddenly causing an issue, and I'm wondering what would have changed between these minor version releases (downgrading back to
4.3.1
fixes the issue) that we might need to account for.The text was updated successfully, but these errors were encountered: