Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork6.6k
fix: worker state#15610
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
fix: worker state#15610
Uh oh!
There was an error while loading.Please reload this page.
Conversation
netlifybot commentedMay 22, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview forjestjs ready!Builtwithout sensitive environment variables
To edit notification comments on pull requests, go to yourNetlify project configuration. |
| * killed off. | ||
| */ | ||
| protected_shutdown():void{ | ||
| // eslint-disable-next-line @typescript-eslint/no-unused-expressions |
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.
funny thing
it was even intentionally ignored before 😅
bd0b248 intojestjs:mainUh oh!
There was an error while loading.Please reload this page.
cpojer commentedMay 22, 2025
Thank you! |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Uh oh!
There was an error while loading.Please reload this page.
Summary
The state was not being correctly updated on exit, which then meant downstream the check for a OOM crash was not detected in tests