You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Haven't been on a windows machine in a while but this is what happens running the test suite on it, I'm assuming it has to do with how getsockname is implemented on windows but I'll look into it.
Traceback (most recent call last):
File "C:\Users\ammar\workspace\pyCraft\tests\test_connection.py", line 62, in _test_connect
self._test_connect_client(client, cond)
File "C:\Users\ammar\workspace\pyCraft\tests\test_connection.py", line 83, in _test_connect_client
client.connect()
File "C:\Users\ammar\workspace\pyCraft\minecraft\networking\connection.py", line 245, in connect
self._connect()
File "C:\Users\ammar\workspace\pyCraft\minecraft\networking\connection.py", line 275, in _connect
self.socket.connect((self.options.address, self.options.port))
OSError: [WinError 10049] The requested address is not valid in its context
The text was updated successfully, but these errors were encountered:
The bound address is 0.0.0.0 which usually implies all
available interfaces, which makes sense when listening
for something. However, when connecting to an address,
a specific address needs to be targeted. Hopefully, any
properly configured computer should have `localhost`
pointing to its loopback interface. Fixes#64
Haven't been on a windows machine in a while but this is what happens running the test suite on it, I'm assuming it has to do with how getsockname is implemented on windows but I'll look into it.
The text was updated successfully, but these errors were encountered: