-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 v8.2.0 #12073
Commits on May 16, 2024
-
test(node): Add test for errors-only ESM app (#12046)
This tests a node app that uses ESM, but no `--import` flag. Somehow this works for `http` (but not other packages...) but this is fine for errors-only mode, for now. Missing: We do show the warning for missing express instrumentation there, still 😬 we may need to tweak this...
Configuration menu - View commit details
-
Copy full SHA for 89377da - Browse repository at this point
Copy the full SHA 89377daView commit details -
feat(browser): Improve idle span handling (#12065)
Closes #12051 This PR does two things: 1. Ensures we add helpful attributes to idle spans more consistently. We now add the `sentry.idle_span_finish_reason` attribute always for idle spans, not only when op == `ui.action.click`. This should also make it easier to debug stuff etc, and I see no reason to not always set this. Additionally, we also keep the number of spans we discarded (if any) for easier debugging too (as `sentry.idle_span_discarded_spans`). 2. We ensure that idle spans cannot exceed the configured `finalTimeout`. Previously, due to the order of things, it was possible that we ended a span very late, if it had a child span with a very late end timestamp (as we took the last child span timestamp). Possibly this could lead to overly long transactions. I think 2, combined with the fact that later we _do_ filter out child spans that ended after idle span, lead to the incorrect-length spans.
Configuration menu - View commit details
-
Copy full SHA for ccb98ff - Browse repository at this point
Copy the full SHA ccb98ffView commit details -
fix(node): Fix check for performance integrations (#12043)
ref #12034 cc @AbhiPrasad when you're back, let's look again at `hasTracingEnabled()` and see if we want to adjust this maybe.
Configuration menu - View commit details
-
Copy full SHA for d634385 - Browse repository at this point
Copy the full SHA d634385View commit details -
fix(browser): Use consistent timestamps (#12063)
In some places we used `Date.now()`, instead of `timestampInSeconds()` which used performance.now(). There are still other places where we use `Date.now()`, esp. in replay and node, but I focused on regular browser stuff for now (because this is most likely to be affected by this).
Configuration menu - View commit details
-
Copy full SHA for 677602f - Browse repository at this point
Copy the full SHA 677602fView commit details -
fix(core): Avoid looking up client for
hasTracingEnabled()
if possi…Configuration menu - View commit details
-
Copy full SHA for 07c6838 - Browse repository at this point
Copy the full SHA 07c6838View commit details -
Merge pull request #12068 from getsentry/master
[Gitflow] Merge master into develop
Configuration menu - View commit details
-
Copy full SHA for 4b18edd - Browse repository at this point
Copy the full SHA 4b18eddView commit details -
fix(core): Export Scope interface as
Scope
(#12067)To make interop with e.g. importing `Scope` from `@sentry/node` easier. Closes #12053
Configuration menu - View commit details
-
Copy full SHA for 4a1f2ac - Browse repository at this point
Copy the full SHA 4a1f2acView commit details -
meta: Fix changelog script (#12069)
Actually we should check for the changelog commit, which we look for by checking `-meta` and `changelog` in the commit message. (Not perfect, but good enough hopefully...) I noticed it was not correctly picking up all commits while a release was in progress before.
Configuration menu - View commit details
-
Copy full SHA for 4003f7e - Browse repository at this point
Copy the full SHA 4003f7eView commit details -
fix(node): Set transactionName for unsampled spans in httpIntegration (…
…#12071) We noticed that in http integration, we were only setting `transactionName` when we had a sampled span. We can actually set this based on the request object we get either way, making this more robust for error-only mode.
Configuration menu - View commit details
-
Copy full SHA for c594d6a - Browse repository at this point
Copy the full SHA c594d6aView commit details -
ref(sveltekit): Warn to delete source maps if Sentry plugin enabled s…
…ource maps generation (#12072) Now we can at least recommend to use `filesToDeleteAfterUpload` since we bumped to vite plugin 2.x with 8.0.0
Configuration menu - View commit details
-
Copy full SHA for bc29d88 - Browse repository at this point
Copy the full SHA bc29d88View commit details -
doc(migration): Add entry for
interactionsSampleRate
(#12064)Configuration menu - View commit details
-
Copy full SHA for 6c37df1 - Browse repository at this point
Copy the full SHA 6c37df1View commit details -
Configuration menu - View commit details
-
Copy full SHA for f1d1a16 - Browse repository at this point
Copy the full SHA f1d1a16View commit details -
feat(redis-cache): Create cache-span with prefixed keys (get/set comm…
…ands) (#12070) Populates the OTel span with cache attributes. Currently, `get` and `set` commands are considered. --------- Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Configuration menu - View commit details
-
Copy full SHA for 257bcb0 - Browse repository at this point
Copy the full SHA 257bcb0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 46511e5 - Browse repository at this point
Copy the full SHA 46511e5View commit details