-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat!: Remove autoSessionTracking
option
#14802
Conversation
size-limit report 📦
|
@@ -6,6 +6,5 @@ window.Sentry = Sentry; | |||
Sentry.init({ | |||
dsn: 'https://[email protected]/1337', | |||
integrations: [captureConsoleIntegration()], | |||
autoSessionTracking: false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iirc, we opted out of session tracking for some tests due to session envelopes colliding with the envelope we're waiting for. Do we need to filter on browserSessionIntegration
instead here? Might as well be old code and this is no longer a concern. I guess we'd find out with the flaky test detector 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point actually. I didn't consider that. I agree though that we would probably catch anything weird in the flakey test detector. Maybe the autoSessionTracking
s here are also from copy and pasting tests.
I will merge this as is cause I'd err on removing unneeded logic. If there are any CI failures coming up we may attribute it to this.
Ref #14609