- 
                Notifications
    You must be signed in to change notification settings 
- Fork 49.7k
[Fiber] Fix missing render times when we cancel a pending commit #31065
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| The latest updates on your projects. Learn more about Vercel for Git ↗︎ 
 | 
| Comparing: 0f1856c...ed4adf3 Critical size changesIncludes critical production bundles, as well as any change greater than 2%: 
 Significant size changesIncludes any change greater than 0.2%: (No significant changes) | 
| setCurrentUpdatePriority(previousUpdateLanePriority); | ||
| } | ||
|  | ||
| return null; | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is unused and mostly removed to have strict types so that commitRoot is assignable to  
| unsuspend: null | (() => void), | 
861ca70    to
    1f67c14      
    Compare
  
    1f67c14    to
    fd8287f      
    Compare
  
    ) DiffTrain build for commit 778e1ed.
Summary
Follow-up to #31016
Fixes
Failed to execute 'measure' on 'Performance': If a non-empty PerformanceMeasureOptions object was passed, at least one of its 'start' or 'end' properties must be present.Not clear why we didn't catch this in our test suite. Probably because the
performancepolyfill does not throw ifstartandendare undefined when a non-empty PerformanceMeasureOptions is passed toperformance.measure?How did you test this change?
5d19e1c8-20240923to04bd67a4-20240924vercel/next.js#70407) where we encountered above bug. Patching the file locally made the test pass: vercel/next.js@744c429(#70407)fninwaitForCommitToBeReady()(fn)does not receive any further arguments. With that change, the bug would've not get passed Flow. The error message isn't as clear as possible but it gives at least a hint that arguments are missing: