Honor Ractor callbacks in direct mode - #384
Closed
OskarEichler wants to merge 1 commit into
Closed
Conversation
OskarEichler
force-pushed
the
codex/direct-ractor-callbacks
branch
from
August 30, 2026 09:21
84e6c99 to
eba807d
Compare
Owner
|
I think I fixed that with some previous PRs already, lmk if any work remains |
Contributor
Author
|
Confirmed against current |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Validate Ractor callback usage before worker-count dispatch and execute the configured callback in zero-worker direct mode.
External map, indexed map, each, and invalid-combination models pass on Ruby 4.0.6 and 3.2.11. Diff and syntax checks pass. Source only; repository tests are unchanged.