Repository navigation
fix: recover runtime task function operations #202
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
Merged
+895
−61
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
When bootstrap fails because a captured function cannot be installed (for example, its serialized source evaluates to
null), callingremoveTaskFunction()for that exact function cannot recover the pool: the worker never installed it, so it rejects the remove request, andawait operation()throws before the pool deletes the captured registration or retries restoration. The worker therefore remains unavailable and every subsequent removal repeats the same failure; removal should be able to discard a pool-side registration that is absent specifically because this worker's bootstrap failed.Useful? React with 👍 / 👎.
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.
Confirmed, and shared with the pinned upstream implementation rather than introduced by the port. Fresh real-worker reproduction on Deno 2.9.7, Bun 1.4.2 and upstream #3369
23357872ffd4737198edf2657bbb96778af22654using Node v26.12.0 threads:badwith a callable whosetoString()returns the stringnull, then start a fixed one-worker pool. Real worker validation rejects replay.Unknown error); captured registration remains and readiness stays false.No ACK/readiness is fabricated. The shared queue retries restoration only after
await operation()succeeds; the failed remove never deletes captured state. The existing #199 success-after-correction scenario is fixed, but deleting the very absent registration needs an additional upstream recovery policy. Leaving this thread open and recording the limitation in the PR description; no independent algorithm change is silently added to this faithful port.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.
Upstream report filed: poolifier/poolifier#3370. The port remains unchanged and faithful to upstream #3369; this recovery-policy change is not folded into PR #202.