meta(changelog): Update changelog for 8.0.0-beta.3 #11698
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…11679) Wwe can streamline our pageload span creation logic now that we actually want to keep the propagation context on the scope after the transaction finished (see #11599). Previously, we'd fork a new scope for the pageload span but IMHO (and according to all our tests) this is no longer necessary.
…ace lifetime tests (#11660) Adds checks for the contents of the `trace` envelope headers in our new `trace-lifetime` test suite. The purpose of these checks is to ensure that we not only propagate and send correct trace data in request headers and Sentry events (trace context) but also in the `trace` envelope header.
…nt trace context (#11681) More clearly shows the current difference in `event.contexts.trace` for error events, depending on if they were sent during an active span or afterwards.
While looking into how we send trace context for error events (today: We only send `trace_id`, `span_id` and `parent_span_id` for errors, while we send everything for transactions. In browser, we always send everything...) I noticed that we don't cover this well for express today. Digging into this, I figured the tests was actually pretty broken, because we didn't have the right import order, so instrumentation was not fully correct 😬 so I split the node-express E2E tests into multiple files, added a test to check the error event shape, and fixed the app setup.
Fixes an oversight from #11628, which was found in the example app.
Now that #11630 was merged in, we can remove `setupGlobalHub`.
Adds `addOpenTelemetryInstrumentation`, a helper that can be used to dynamically register OpenTelemetry instrumentation. This helps unblock work on #11548 The helper itself is quite small: ```ts export function addOpenTelemetryInstrumentation( instrumentation: InstrumentationOption | InstrumentationOption[], ): void { registerInstrumentations({ instrumentations: Array.isArray(instrumentation) ? instrumentation : [instrumentation], }); } ``` and is designed to accept either a standalone instrumentation or an array of instrumentations. This gives users a ton of flexibility into usage!
Instead of using `this.endSession`, directly use `endSession`.
This ports `packages/browser/test/integration/suites/onerror.js` to playwright. Because I couldn't throw top level errors without generating script errors, I elected to simulate `window.onerror` being called. Co-authored-by: Lukas Stracke <[email protected]>
… fetch instrumentation (#11686)
size-limit report 📦
|
s1gr1d
approved these changes
Apr 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.