-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
SessionFlusher ignores enabled_environments config #2234
Labels
Comments
yep need to add a check there, thanks for reporting! |
I can take a look at this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
Recently we started using Sentry Releases feature, which required adding this configuration into our Sentry initializer:
Unfortunately, even having enabled only
staging
andproduction
environments, Sentry gem still tries to send Session info in thedevelopment
environment (where we have fakedsn
). This leads to the next error in the logs in 1 minutes after rails server boot and processing the first request:Reproduction Steps
$ rails new test-sentry-ruby
$ cd test-sentry-ruby
$ bundle add sentry-ruby sentry-rails
config/initializers/sentry.rb
with the next configuration:rails server
and open the home page in the browser - http:https://localhost:3000/development.log
fileExpected Behavior
No Sentry-related errors in logs as
development
env is not listed inenabled_enviroments
.Actual Behavior
Bunch of errors in
development.log
file:Ruby Version
3.2.2
SDK Version
5.16.1 (also confirmed in 5.5)
Integration and Its Version
Rails = 7.1.2 (also confirmed in Rails 7.0.4)
Sentry Config
The text was updated successfully, but these errors were encountered: