Skip to content

fix(replay): Start replay in afterAllSetup instead of next tick #12709

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

Merged
merged 3 commits into from
Jul 2, 2024

Conversation

mydea
Copy link
Member

@mydea mydea commented Jul 1, 2024

This should hopefully fix some race conditions.

Instead of initializing replay in the next tick, do it in the current tick but in afterAllSetup, to ensure this runs e.g. after the replay-canvas integration.

Fixes #12707

@mydea mydea self-assigned this Jul 1, 2024
Copy link
Contributor

github-actions bot commented Jul 1, 2024

size-limit report 📦

Path Size
@sentry/browser 22.22 KB (0%)
@sentry/browser (incl. Tracing) 33.38 KB (0%)
@sentry/browser (incl. Tracing, Replay) 69.12 KB (-0.06% 🔽)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.45 KB (-0.07% 🔽)
@sentry/browser (incl. Tracing, Replay with Canvas) 73.18 KB (-0.06% 🔽)
@sentry/browser (incl. Tracing, Replay, Feedback) 85.8 KB (-0.03% 🔽)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics) 87.66 KB (-0.03% 🔽)
@sentry/browser (incl. metrics) 26.5 KB (0%)
@sentry/browser (incl. Feedback) 38.86 KB (0%)
@sentry/browser (incl. sendFeedback) 26.84 KB (0%)
@sentry/browser (incl. FeedbackAsync) 31.45 KB (0%)
@sentry/react 24.97 KB (0%)
@sentry/react (incl. Tracing) 36.43 KB (0%)
@sentry/vue 26.33 KB (0%)
@sentry/vue (incl. Tracing) 35.24 KB (0%)
@sentry/svelte 22.36 KB (0%)
CDN Bundle 23.42 KB (0%)
CDN Bundle (incl. Tracing) 35.12 KB (0%)
CDN Bundle (incl. Tracing, Replay) 69.22 KB (-0.05% 🔽)
CDN Bundle (incl. Tracing, Replay, Feedback) 74.41 KB (-0.06% 🔽)
CDN Bundle - uncompressed 68.8 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed 103.82 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed 214.21 KB (-0.04% 🔽)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 226.92 KB (-0.04% 🔽)
@sentry/nextjs (client) 36.3 KB (0%)
@sentry/sveltekit (client) 34.02 KB (0%)
@sentry/node 130.62 KB (0%)
@sentry/node - without tracing 91.64 KB (-0.01% 🔽)
@sentry/aws-serverless 116.82 KB (+0.01% 🔺)

@mydea mydea changed the title fix(replay): Start replay immediately, not in next tick fix(replay): Start replay in afterAllSetup instead of next tick Jul 1, 2024
@mydea mydea force-pushed the fn/replayImmediateError branch from bacf357 to eeae961 Compare July 1, 2024 11:46
@mydea mydea marked this pull request as ready for review July 1, 2024 12:59
@mydea mydea requested a review from a team as a code owner July 1, 2024 12:59
Comment on lines 296 to 298
if (!this._replay) {
return;
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we remove this now?

@@ -133,8 +134,8 @@ describe('Integration | coreHandlers | handleGlobalEvent', () => {

it('tags errors and transactions with replay id for session samples', async () => {
const { replay, integration } = await resetSdkMock({});
// @ts-expect-error protected but ok to use for testing
integration._initialize();
integration['_initialize'](getClient()!);
Copy link
Member

@s1gr1d s1gr1d Jul 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

omg this syntax 😅 Not wrong at all, just JS/TS 🙄 😆

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, it is definitely weird, but I prefer this over having to do @ts-expect-error 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Capture errors for Replay that happen immediately after init
3 participants