Use PIPE_NOWAIT on Windows to avoid blocking on writes #781
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
compnerd
reviewed
Mar 6, 2023
|
@swift-ci please test |
|
@swift-ci please test Windows platform |
1 similar comment
|
@swift-ci please test Windows platform |
compnerd
reviewed
Mar 7, 2023
|
@swift-ci please test |
|
@swift-ci please test Windows platform |
|
@swift-ci please test |
|
@swift-ci please test Windows platform |
|
I ran tests locally. 22/22 passed. |
This was referenced Jan 24, 2025
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.
libdispatchdepends on non-blocking writes to retry later. For pipes on Windows, we achieved this usingNtQueryInformationFileto get theWriteQuotaAvailablefor the pipe, but this function returns0when there is a blocking read on the receiver side (this appears to be an OS bug), which causes us to never proceed to the write.This change rather sets
PIPE_NOWAITon the pipe's write handle, similar to what is done on other platforms. This call will fail if the pipe handle does not haveFILE_WRITE_ATTRIBUTESset, which is not a problem with the typical case of using aFoundation.Pipe. If we cannot setPIPE_NOWAIT, we will proceed with blocking writes, which in some circumstances could lead to hangs.This resolves an issue with
SourceKit-LSPon Windows where tests and real-life scenarios would hang because a pipe could never be written to.