meta(changelog): Update changelog for 8.0.0-rc.2 #11950
Merged
Conversation
This file contains hidden or 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
[Gitflow] Merge master into develop
This prints a warning if we detect that the koa app passed to setupKoaErrorHandler is not instrumented. This happens if you import koa before calling Sentry.init.
This prints a warning if we detect that the express `app` passed to `setupExpressErrorHandler` is not instrumented. This happens if you import express _before_ calling Sentry.init: <img width="877" alt="image" src="https://github.com/getsentry/sentry-javascript/assets/2411343/1af41fb9-06f5-4478-8be0-72c46568da14">
Aaand another one...
Another one...!
The user can be set on any scope, we should pick it correctly from wherever it is set.
When using `setupFastifyErrorHandler(app)` we can check if the app was correctly instrumented. Not sure how to best test this - I tested this manually in a test app and could verify that the log was printed when requiring fastify before calling init!
No need to have the `-app` suffix there.
Closes #11766 These tests are also in TypeScript so they check the types too. I found that two out of three cron libraries were actually swallowing exceptions so that they were not captured by Sentry. I added calls to `captureException` to rectify that.
…y/instrumentation` to `0.51.1` (#11941)
Use vitest instead of jest. Some notes: * Use vi/jest `*Async` fake timer functions instead of `process.nextTick` * Our `useFakeTimers` module was setting an interval which was causing all sorts of flakes in tests with the updated fake timers library * removed the interval in `use-fake-timers` module which seemed to be unnecessary and was causing lots of flakes in our tests (also was able to remove all of the random tick values in timestamps due to this)
size-limit report 📦
|
Lms24
approved these changes
May 8, 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.