Flaky test [Windows] ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_ip_client_ip [API-2341]
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- À l'abandon
- Stack technique
- python
- Domaine
- distributed-systems, testing-qa
Piste de recherche
Commencez par ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_ip_client_ip et le journal d’échec de Windows Python 3.13. Inspectez hazelcast/internal/asyncio_connection.py autour de _connect et _on_auth, reproduisez le test sous Windows et identifiez une correction stable ou un ajustement du test qui supprime les erreurs de socket tout en préservant le nombre de connexions attendu.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
- Langage dominant
- Python
- Étoiles
- 115
- Forks
- 78
- Merge moyen
- 2 j 23 h
- PR mergées (30 j)
- 2
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de hazelcast/hazelcast-python-client
-
Type: Test-Failure
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
-
Type: Test-Failure
Difficulté 3/5 1-2 jours Accessibilité débutants 52/100
-
asyncio Type: Test-Failure
Difficulté 4/5 3-5 jours Accessibilité débutants 38/100
-
asyncio to-jira Type: Test-Failure
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
hazelcast/hazelcast-python-client#760 · 1 commentaire ·
-
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
Toutes les issues de hazelcast/hazelcast-python-client
Issues similaires
-
bug triage
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
ultralytics/ultralytics#27258 ·
Les mainteneurs répondent en général sous 1 jour
-
author-page correction move-papers
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
acl-org/acl-anthology#10969 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 86/100
Les mainteneurs répondent en général sous 1 jour
-
Pin Python to 3.14 in the era5grib-parallel environment specificationPeut-être pris @atteggiani l’a pris aujourd’hui. Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 85/100
ACCESS-NRI/containerised-environments-infra#129 ·
Les mainteneurs répondent en général sous 2 jours
-
priority middle
Difficulté 1/5 Moins d'une heure Accessibilité débutants 72/100
KATO-Hiro/AtCoderClans#13029 ·
Les mainteneurs répondent en général sous 1 jour