-
Notifications
You must be signed in to change notification settings - Fork 49.5k
[Flight] Improve aborted hanging promise stacks #34638
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
base: main
Are you sure you want to change the base?
Conversation
Comparing: dce1f6c...f1b6be1 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) |
4beef64
to
edff0c1
Compare
edff0c1
to
7e9699b
Compare
8f746a7
to
4c3a1fa
Compare
4c3a1fa
to
f1b6be1
Compare
// it's a point of interest. | ||
|
||
// If the awaited node was an await in user space, that will typically have a more | ||
// useful stack. Try to find one, before falling back to using the promise node. |
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 not right. If that was the case, we could always just use the await, but we don't. We provide both (and often favor the I/O one for presentation).
The question is, why isn't the "await" already in the data as the await node and why isn't the frontend (probably Fizz in this case) picking that one over the I/O if the I/O is missing stack?
No description provided.