You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some leftover usages of span.startChild(). Some of them are related to #10898, but others are standalone and should be refactored to just create a span based on the active span.
In most cases, we can probably refactor them to just use startInactiveSpan instead, unless we need the span to be active (which is rarely the case, as far as I could see).
I would ignore the usage in old node for now, we can remove this eventually.
### Tasks
- [ ] https://github.com/getsentry/sentry-javascript/pull/10956
- [ ] https://github.com/getsentry/sentry-javascript/pull/10943
- [x] MAYBE: Refactor `startChild` usage in node & node performance integrations - probably safe to ignore this for now
The text was updated successfully, but these errors were encountered:
mydea
changed the title
[v8] Refactor usages of span.startChild
[v8] Refactor usages of span.startChild() to startInactiveSpan()Mar 4, 2024
This rewrites browser metrics to:
1. Accept spans instead of transactions
2. Use the new performance APIs instead of the old ones
The only thing I left for now is the tags, which we can get rid of
separately: #10823
Part of #10900
Uh oh!
There was an error while loading. Please reload this page.
We have some leftover usages of
span.startChild()
. Some of them are related to #10898, but others are standalone and should be refactored to just create a span based on the active span.In most cases, we can probably refactor them to just use
startInactiveSpan
instead, unless we need the span to be active (which is rarely the case, as far as I could see).I would ignore the usage in old node for now, we can remove this eventually.
The text was updated successfully, but these errors were encountered: