Problem: ipc connect can fail on Windows, even after bind #4734
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.
Solution:
$env:TMP
)_w
back toretired_fd
after closing itAlso addresses todo item to remember the tcpip fallback after ipc has failed once, so the failing path doesn't get retried every time. I can back that out if folks want.
I believe this actually closes #4730, though after some debugging, I do believe there are still missing checks to
signaler::valid()
, because even when make_fd_pair properly fails, send is still called on the invalid signaler, leading to the EBADFD reported in #4730, when it seems like it should probably be an assert in the signaler constructor (or immediately after calling the constructor) that it failed to create an fd pair.