-
Notifications
You must be signed in to change notification settings - Fork 2
feat!: annotate SQL statements with OTel trace context via AtomicOperation #154
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Annotation ignores post-hoc span instrument
Medium Severity
annotated_sql/current_traceparentrun synchronously whenfetch_manyorfetch_optionalis called, before the returned future or stream is polled. Attaching a span with.instrument(span)after.execute(...)/.fetch_*(...)therefore sees no active context and silently skips thetraceparentcomment, even though the span is current while the query runs.#[instrument]on an enclosing async function still works because the span is entered before those calls.Reviewed by Cursor Bugbot for commit 4f6be80. Configure here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Acknowledged — the observation is technically correct: the annotation decision runs at call time, before the returned future/stream is polled, so
.instrument(span)attached directly to a fetch future misses thetraceparentcomment.Marking as won't-fix:
#[tracing::instrument]attributes, and the supported pattern for manual spans is instrumenting an enclosing async block (seetests/trace_annotation.rs) — in both cases the span is active at call time and annotation works.Span::current()captured in constructors), and deferring the check into the future would force aBox::pinonto the unannotated fast path, which currently returns the inner future directly.If a real downstream use case for post-hoc instrumentation of raw fetch futures shows up, the fix is small (~20 lines: move the
annotated_sql()check inside the returned future/stream) and can land as a follow-up.