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.
TL;DR
VS Code users at my company are facing a bug that at first sight seemed to be linked to the IDE (because our unit tests run from the command line), but which in reality is related to a
pytest-socket
bug (highlighted by the creation of a socket on the hostnamelocalhost
by the vscode-python extension).Problem
Our following code from
conftest.py
makes it impossible to use the Testing tab in VS Code (no matter which unit test is run).Error observed:
Why?
The error message from
pytest-socket
is wrong:localhost
is not compared tolocalhost
,127.0.0.1
and::1
.127.0.0.1
,127.0.0.1
and::1
.This is because the allowed hosts used for comparison are previously converted to IP addresses. Therefore, a comparison with a host that is not an IP address can never succeed.
Affected versions
pytest-socket
version0.6.0
0.5.1
Diagnostic data
VS Code info
Extension version
Related issues / PR
This PR resolves: