Files
Ignacy Łątka 4d0a5c4454 fix(react-profiler): validate CPU sample array elements, not just their length
Array-ness and equal length were not enough: `intervalStartsMs: [{}, {}, {}]`
passed the guard and `profiler-cpu-query` still printed NaN in every column,
the exact symptom #950 reports, and string node ids still produced a confident
"all of them were idle - the JS thread was not executing".

Check each of the three parallel arrays down to the element with
`Number.isFinite`, which also rejects the `null` that `JSON.stringify` writes
for a non-finite float and that `Float64Array` would read back as a silent 0.

The `nodes` and `version` clauses had no test that could fail on their own -
the only fixture reaching them tripped every clause at once - so each rejected
shape is now its own case.
2026-09-09 22:58:44 +02:00
..