feat(core): Use getActiveSpan instead of _getSpanFromScope for logs & metrics - #23223
feat(core): Use getActiveSpan instead of _getSpanFromScope for logs & metrics#23223mydea wants to merge 1 commit into
getActiveSpan instead of _getSpanFromScope for logs & metrics#23223Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3b4dd9c. Configure here.
| } | ||
|
|
||
| const span = _getSpanForScope(currentScope); | ||
| const span = getActiveSpan(currentScope); |
There was a problem hiding this comment.
Feat PR lacks integration tests
Low Severity
Flagged because it was mentioned in the PR review rules file: feat PRs need at least one integration or E2E test. This change switches logs and metrics span lookup to getActiveSpan, which mainly affects Node/OTEL correlation, but the PR adds no test covering that. Existing metrics suites already emit inside startSpan without asserting span_id / sentry.trace.parent_span_id.
Additional Locations (1)
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 3b4dd9c. Configure here.
size-limit report 📦
|


Use this API instead of a stack-specific one.