-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
meta(changelog): Update changelog for 9.7.0 #15755
Merged
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
Exposes `sentryHandleError` for `@sentry/remix/cloudflare`. Closes: #15620
[Gitflow] Merge master into develop
…ntation (#15732) Part of #15730 Noticed that this is not really happening otherwise, so if we are not adding the `HttpInstrumentation` we now make sure to extract incoming traces ourselves! This will unlock us not adding that instrumentation when tracing is disabled. Also includes #15731 as a side effect.
) Small optimization to avoid unnecessary work. ref: #15725
## Description `captureLog` takes in a `log` interface as well as a scope, and constructs a serialized log to send to Sentry. Instead of directly sending the serialized log, it adds it to a log buffer that is flushed based on some strategy. As a fallback, the buffer flushes itself when it gets over 100 items, which ensures we never get a payload thats too large. The browser and server runtime client are expected to add more advanced flushing strategies on top of the simple implementation exposed in `captureLog`. This will be done in future PRs. The serialized log that is constructed by `captureLog` send logs via the opentelemetry format. This is temporary, in the future we'll switch to the sentry logs protocol, but while that gets ready we are using the OTEL one. ## Next steps 1. Add flushing strategy for server-runtime-client 2. Implement top-level API methods as per develop spec 3. Add support for paramaterized strings 4. Add integration tests to validate envelope gets sent correctly
This just makes it a bit more disoverable for poor souls like me searching for "alpha" in this doc --------- Co-authored-by: Francesco Gringl-Novy <[email protected]>
size-limit report 📦
|
Lms24
approved these changes
Mar 20, 2025
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.