[Flight] Promote enableAsyncDebugInfo to stable without enableComponentPerformanceTrack #33996
+83
−50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's a lot of overlap between
enableComponentPerformanceTrackandenableAsyncDebugInfobecause they both rely on timing information. The former is mainly emit timestamps for how long server components and awaits took. The latter how long I/O took.enableAsyncDebugInfois currently primarily for the component performance track but its meta data is useful for other debug tools too. This promotes that flag to stable.However,
enableComponentPerformanceTrackneeds more work due to performance concerns with Chrome DevTools so I need to separate them. This keeps doing most of the timing tracking on the server but doesn't emit the per-server component time stamps whenenableComponentPerformanceTrackis false.