-
Notifications
You must be signed in to change notification settings - Fork 8
fix(tracing) batch span events in SGPAsyncTracingProcessor #342
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
81e2021
fix(tracing): batch span events in SGPAsyncTracingProcessor
mohammadatallah-scale e6ea039
refactor(tracing): split _run worker into named helpers and expand tests
mohammadatallah-scale 82e2f8e
feat(tracing): log disabled-state warning once at init plus 4 edge-ca…
mohammadatallah-scale a4dac78
fix(tracing): import APIError from scale_gp_beta public module (CI lint)
mohammadatallah-scale 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
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.
sgp_span.inputno longer updated on span endon_span_endpreviously containedsgp_span.input = span.input, which allowed callers to augment the input between start and end (the canonical case being LLM conversation messages that grow as the turn completes). That line is absent from this PR; the end-enqueue only carriesoutput,metadata, andend_time. Any caller that setsspan.inputafteron_span_start— exactly the scenario exercised bytest_sgp_span_input_updated_on_end— will have the stale start-time input persisted to SGP instead of the final value.The test was updated to check batching mechanics but the assertion that the updated input reached the upsert was removed, hiding this regression. If the intent is to intentionally align with the sync processor (which also skips
inputon end), that should be documented in the PR description and the test should be renamed to remove the misleading "input updated on end" framing.Prompt To Fix With AI