Flaky test [Windows] ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_ip_client_ip [API-2341]
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- python
- Ambito
- distributed-systems, testing-qa
Direzione di ricerca
Inizia con ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_ip_client_ip e il log di errore di Windows Python 3.13. Esamina hazelcast/internal/asyncio_connection.py intorno a _connect e _on_auth, riproduci il test su Windows e individua una correzione stabile o un adeguamento del test che elimini gli errori del socket preservando il numero di connessioni previsto.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
This test seems to fail only on Windows with Python 3.13.
https://github.com/hazelcast/hazelcast-python-client/actions/runs/20093655098/job/57646703236
Log:
ERROR asyncio:base_events.py:1879 Exception in callback _ProactorBasePipeTransport._call_connection_lost(OSError(10057..., 10057, None))
handle: <Handle _ProactorBasePipeTransport._call_connection_lost(OSError(10057..., 10057, None)) created at C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py:152>
source_traceback: Object created at (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\runners.py", line 118, in run
return self._loop.run_until_complete(task)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 712, in run_until_complete
self.run_forever()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 683, in run_forever
self._run_once()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 2042, in _run_once
handle._run()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\events.py", line 89, in _run
self._context.run(self._callback, *self._args)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 316, in _loop_reading
self._fatal_error(exc, 'Fatal read error on pipe transport')
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 132, in _fatal_error
self._force_close(exc)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 152, in _force_close
self._loop.call_soon(self._call_connection_lost, exc)
Traceback (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\events.py", line 89, in _run
self._context.run(self._callback, *self._args)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 165, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
OSError: [WinError 10057] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied
INFO hazelcast.internal.asyncio_connection:asyncio_connection.py:1015 <hazelcast.internal.asyncio_reactor.AsyncioConnection object at 0x0000015632BA63F0> closed. Reason: Connection closed by server
WARNING hazelcast.internal.asyncio_connection:asyncio_connection.py:581 Error during initial connection to Member [127.0.0.1]:5701 - 71936b64-69c0-464e-ae41-14042871f73e
Traceback (most recent call last):
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 576, in _connect
return await get_or_connect_func(target)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 404, in _get_or_connect_to_member
await self._on_auth(response, connection)
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 624, in _on_auth
raise e
File "D:\a\hazelcast-python-client\hazelcast-python-client\hazelcast\internal\asyncio_connection.py", line 620, in _on_auth
response = await response
^^^^^^^^^^^^^^
hazelcast.errors.TargetDisconnectedError: TargetDisconnectedError
INFO hazelcast.internal.asyncio_connection:asyncio_connection.py:574 Trying to connect to Address(host=127.0.0.1, port=5702)
WARNING hazelcast.internal.asyncio_reactor:asyncio_reactor.py:278 Connection closed by server
ERROR asyncio:base_events.py:1879 Exception in callback _ProactorBasePipeTransport._call_connection_lost(OSError(10057..., 10057, None))
handle: <Handle _ProactorBasePipeTransport._call_connection_lost(OSError(10057..., 10057, None)) created at C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py:152>
source_traceback: Object created at (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\runners.py", line 118, in run
return self._loop.run_until_complete(task)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 712, in run_until_complete
self.run_forever()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 683, in run_forever
self._run_once()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\base_events.py", line 2042, in _run_once
handle._run()
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\events.py", line 89, in _run
self._context.run(self._callback, *self._args)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 316, in _loop_reading
self._fatal_error(exc, 'Fatal read error on pipe transport')
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 132, in _fatal_error
self._force_close(exc)
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 152, in _force_close
self._loop.call_soon(self._call_connection_lost, exc)
Traceback (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\events.py", line 89, in _run
self._context.run(self._callback, *self._args)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\hostedtoolcache\windows\Python\3.13.9\x64\Lib\asyncio\proactor_events.py", line 165, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
- Lingua principale
- Python
- Stelle
- 115
- Fork
- 78
- Merge medio
- 2g 23h
- PR unite (30g)
- 2
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di hazelcast/hazelcast-python-client
-
Type: Test-Failure
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Type: Test-Failure
Difficoltà 3/5 1-2 giorni Idoneità per principianti 52/100
-
asyncio Type: Test-Failure
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
-
asyncio to-jira Type: Test-Failure
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
hazelcast/hazelcast-python-client#760 · 1 commento ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
Tutte le issue di hazelcast/hazelcast-python-client
Issue simili
-
bug good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
aws-samples/sample-spec-driven-presentation-maker#648 ·
I maintainer di solito rispondono entro 1 giorno
-
firestore: enable live window.yaml pipeline system tests once add_window_fields is in productionAperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 64/100
googleapis/google-cloud-python#19115 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Feyisara2108/stellargive#1377 ·
I maintainer di solito rispondono entro 1 giorno
-
CRS WKT default to WKT2Apertaenhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno