Skip to content

Conversation

unstubbable
Copy link
Collaborator

No description provided.

@meta-cla meta-cla bot added the CLA Signed label Sep 28, 2025
@github-actions github-actions bot added the React Core Team Opened by a member of the React Core Team label Sep 28, 2025
@react-sizebot
Copy link

react-sizebot commented Sep 28, 2025

Comparing: dce1f6c...f1b6be1

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name +/- Base Current +/- gzip Base gzip Current gzip
oss-stable/react-dom/cjs/react-dom.production.js = 6.68 kB 6.68 kB +0.05% 1.83 kB 1.83 kB
oss-stable/react-dom/cjs/react-dom-client.production.js = 536.10 kB 536.10 kB = 94.79 kB 94.79 kB
oss-experimental/react-dom/cjs/react-dom.production.js = 6.69 kB 6.69 kB = 1.83 kB 1.83 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js = 663.69 kB 663.69 kB = 117.00 kB 117.00 kB
facebook-www/ReactDOM-prod.classic.js = 687.59 kB 687.59 kB = 121.04 kB 121.04 kB
facebook-www/ReactDOM-prod.modern.js = 678.02 kB 678.02 kB = 119.39 kB 119.39 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against f1b6be1

@unstubbable unstubbable changed the title [Flight] Add a test for aborted hanging promise stacks [Flight] Add a failing test for aborted hanging promise stacks Sep 29, 2025
@unstubbable unstubbable changed the title [Flight] Add a failing test for aborted hanging promise stacks [Flight] Improve aborted hanging promise stacks Sep 29, 2025
// 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.
Copy link
Collaborator

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed React Core Team Opened by a member of the React Core Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants