add elements to step_end in Trace #114
Merged
+416
−120
Conversation
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
rcholic
pushed a commit
that referenced
this pull request
Jan 6, 2026
add elements to step_end in Trace
rcholic
pushed a commit
that referenced
this pull request
Jan 10, 2026
add elements to step_end in Trace
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Benefits Achieved
✅ Byte-range optimization still works - Step_end events can be fetched individually
✅ Diff overlay works immediately - No need to load full trace events
✅ Self-contained steps - Each step_end has complete snapshot data with diff_status
✅ Backward compatible - Frontend already checks for elements in multiple locations
✅ Fully tested - Both SDKs have comprehensive test coverage