Skip to content

api: Handling non-symbolized frames properly for flamecharts#6143

Merged
manojVivek merged 1 commit into
mainfrom
flamechart-api-error-handling
Jan 8, 2026
Merged

api: Handling non-symbolized frames properly for flamecharts#6143
manojVivek merged 1 commit into
mainfrom
flamechart-api-error-handling

Conversation

@manojVivek
Copy link
Copy Markdown
Contributor

@manojVivek manojVivek commented Jan 8, 2026

The Non-symbolized frames were causing the runtime error: index out of range [0] with length 0 error while rendering the flamechart, this handles it.

@alwaysmeticulous
Copy link
Copy Markdown

alwaysmeticulous Bot commented Jan 8, 2026

✅ Meticulous spotted 0 visual differences across 328 screens tested: view results.

Meticulous evaluated ~4 hours of user flows against your PR.

Expected differences? Click here. Last updated for commit 910a956. This comment will update as new commits are pushed.

@manojVivek manojVivek merged commit 464c52b into main Jan 8, 2026
35 checks passed
@manojVivek manojVivek deleted the flamechart-api-error-handling branch January 8, 2026 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants