Repository navigation
docs(attachments): Flatten flame graph node references - #20073
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
added
sdk-develop-docs
philprime
marked this pull request as ready for review
October 19, 2026 09:10
Contributor
|
Rollouts skipped this pull request: Only application-repo documentation changed (a single develop-docs .mdx file), which matches the criteria to skip documentation-only changes that do not ship t… Mention |
jjbayer
approved these changes
Oct 19, 2026
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
DESCRIBE YOUR PR
The draft flame graph attachment format now stores nodes in a flat top-level
nodesarray. Bothchildrenand treerootsuse zero-based node indices, avoiding deeply nested JSON and allowing iterative processing without recursion-related stack overflows in SDKs and ingestion consumers.Tree grouping retains thread metadata and independent sample populations. The contract defines reference bounds and tree constraints, and explains how inline expansion updates node references. The payload example follows the flat format.
IS YOUR CHANGE URGENT?