Improve errno detection for failed connections without ext-sockets #304
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.
This changeset improves errno detection for failed connections without ext-sockets. Reporting the errstr already works on most platforms even when
ext-sockets
is not installed, consistently reporting the correct errno previously requiredext-sockets
. With these changes applied, we now also take the errno constants fromext-pcntl
andext-posix
into account. This is particularly useful for lightweight container images (Docker) that by default come withext-sockets
andext-pcntl
disabled butext-posix
enabled. All extensions remain entirely optional.Link dump:
Builds on top of #271, #267, #266 and others