fix: worker state #15610
Merged
fix: worker state #15610
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Smrtnyk
reviewed
May 22, 2025
| @@ -125,8 +125,7 @@ export default abstract class WorkerAbstract | |||
| * killed off. | |||
| */ | |||
| protected _shutdown(): void { | |||
| // eslint-disable-next-line @typescript-eslint/no-unused-expressions | |||
There was a problem hiding this comment.
funny thing
it was even intentionally ignored before 😅
cpojer
approved these changes
May 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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
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