Skip to content
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

Always bail out timed out children even if they receive an update #13901

Merged
merged 2 commits into from
Oct 20, 2018

Conversation

acdlite
Copy link
Collaborator

@acdlite acdlite commented Oct 20, 2018

The fragment that wraps timed-out children should always have an expiration time of NoWork.

@sophiebits
Copy link
Collaborator

wow, whoever paired on this with you must be really smart

@sizebot
Copy link

sizebot commented Oct 20, 2018

Details of bundled changes.

Comparing: 0fc0446...5c466bb

scheduler

File Filesize Diff Gzip Diff Prev Size Current Size Prev Gzip Current Gzip ENV
scheduler.development.js n/a n/a 0 B 19.17 KB 0 B 5.74 KB UMD_DEV
scheduler.production.min.js n/a n/a 0 B 3.16 KB 0 B 1.53 KB UMD_PROD

Generated by 🚫 dangerJS

The fragment that wraps timed-out children should always have an
expiration time of NoWork.
@acdlite acdlite merged commit e16cdd5 into facebook:master Oct 20, 2018
linjiajian999 pushed a commit to linjiajian999/react that referenced this pull request Oct 22, 2018
…cebook#13901)

* Always bail out timed out children even if they receive an update

The fragment that wraps timed-out children should always have an
expiration time of NoWork.

* Don't need to set expirationTime, only childExpirationTime
jetoneza pushed a commit to jetoneza/react that referenced this pull request Jan 23, 2019
…cebook#13901)

* Always bail out timed out children even if they receive an update

The fragment that wraps timed-out children should always have an
expiration time of NoWork.

* Don't need to set expirationTime, only childExpirationTime
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants