mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-14 18:01:20 +08:00
fac9bb8f44
Backstop for the same defect the unpause fixes. A timeline that owns children yet reports a duration of 0 cannot be correct, and the symptom is an entirely black render that lint, check and validate all pass, because none of them looks at pixels. There is no legitimate composition where children span time and the total is zero, so the check has no false-positive case. Anything that reaches it has a cause the unpause did not cover, which is exactly the case worth hearing about rather than capturing frozen frames in silence. Emitted to the console because the capture session forwards browser console output into the producer's diagnostics, which is the channel a render actually surfaces. Verified by disabling the unpause and rendering the reported composition: the warning fires through the real pipeline, naming the composition id and the child count.