Skip to content

ui: Handle undefined BigInt values properly#5961

Merged
yomete merged 1 commit into
mainfrom
flamegraph-nodes-bigint
Sep 18, 2025
Merged

ui: Handle undefined BigInt values properly#5961
yomete merged 1 commit into
mainfrom
flamegraph-nodes-bigint

Conversation

@yomete
Copy link
Copy Markdown
Contributor

@yomete yomete commented Sep 18, 2025

This PR updates the null checks for cumulativeColumn and diffColumn values in both FlameGraphNodes.tsx and useVisibleNodes.ts to use != null instead of !== null, ensuring undefined values are handled properly.

It also fixes a memoization cache bug in useVisibleNodes that caused missing flame graph nodes when switching between data states/modifying the URL state, by adding table.numRows to the cache key.

And lastly, I modified the invert call stack button in InvertCallStack/index.tsx to reset the flame graph state when toggling.

@alwaysmeticulous
Copy link
Copy Markdown

alwaysmeticulous Bot commented Sep 18, 2025

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

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

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

const handleSetInvert = (value: boolean): void => {
setInvertStack(value ? 'true' : '');

resetFlameGraphState();
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reset the flame graph expansion when inverting the call stack

@yomete yomete merged commit f094011 into main Sep 18, 2025
37 of 38 checks passed
@yomete yomete deleted the flamegraph-nodes-bigint branch February 13, 2026 10:46
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