Pass IO::WRITABLE, not FMODE_WRITABLE, to the scheduler's io_wait - #9733
Open
sampokuokkanen wants to merge 1 commit into
Open
sampokuokkanen wants to merge 1 commit into
sampokuokkanen wants to merge 1 commit into
Conversation
ioWaitReadable and ioWaitWritable passed OpenFile's mode flags as the event mask. READABLE happens to match IO::READABLE, but WRITABLE is 2, which is IO::PRIORITY, so a write that hit EAGAIN asked the scheduler to wait for priority data. io-event's select backend then never put the IO in the writable set and the writer hung. Use the IO event values like MRI's rb_fiber_scheduler_io_wait_writable.
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.
ioWaitReadableandioWaitWritablepassed OpenFile's mode flags as the event mask.READABLEhappens to matchIO::READABLE, butWRITABLEis 2, which isIO::PRIORITY, so a write that hit EAGAIN asked the scheduler to wait for priority data. io-event's select backend then never put the IO in the writable set and the writer hung.Use the IO event values like MRI's
rb_fiber_scheduler_io_wait_writable.