Skip to content

fix: Honour enabled: false for envelopes forwarded from renderers and utility processes - #1432

Merged
timfish merged 1 commit into
masterfrom
fix/enabled-false-forwarded-envelopes
Sep 17, 2026
Merged

timfish merged 1 commit into
masterfrom
fix/enabled-false-forwarded-envelopes

Conversation

@timfish

@timfish timfish commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

When the main process is initialised with enabled: false, events from renderers are dropped because they go through captureEvent. Spans, replay and profile chunk envelopes from renderers, and non-event envelopes from utility processes, were still sent. Main forwarded them with getClient()?.getTransport()?.send(envelope), which skips the client's enabled check.

This sends them through client.sendEnvelope instead. It checks enabled and the transport, and resolves {} when it does not send. It also emits beforeEnvelope; both listeners in main (normalizePaths, rendererProfiling) ignore these envelope types, so nothing else changes.

Adds an e2e test app with enabled: false in main and replay plus tracing in the renderer. It fails without this change and passes with it.

Found while reviewing #1429, which works around the same problem with its own enabled checks.

… utility processes

Main sent renderer spans, replay, profile chunks and utility process
non-event envelopes straight to the transport, which skips the client's
enabled check. Send them through client.sendEnvelope instead.
@timfish
timfish enabled auto-merge (squash) September 17, 2026 14:18
@timfish
timfish merged commit 88fcf00 into master Sep 17, 2026
116 checks passed
@timfish
timfish deleted the fix/enabled-false-forwarded-envelopes branch September 17, 2026 14:27
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.

2 participants