[test] Fix WebsockifyServerHarness on ipv6 enabled machine. NFC #22822
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
The test_nodejs_sockets_echo_subprotocol_runtime test was failing on my machine because node was resolving "localhost" to the IPv6 address ::1 but the websockify server was running on the IPv4 address 127.0.0.1.
kripken
approved these changes
Oct 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The test_nodejs_sockets_echo_subprotocol_runtime test was failing on my machine because node was resolving "localhost" to the IPv6 address ::1 but the websockify server was running on the IPv4 address 127.0.0.1.
The only thing that
source_is_ipv6=Truedoes is setprefer_ip6which in turn just reveres the list of results from the DNS lookup: https://github.com/novnc/websockify/blob/417210f2cf8db9cd3cd9d86c45ef954778176b0e/websockify/websockifyserver.py#L454-L455