Flaky test [Windows] ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_ip_client_ip [API-2341]

Offen
#761 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
python

Rechercherichtung

Beginne mit ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_ip_client_ip und dem Windows Python 3.13-Fehlerprotokoll. Untersuche hazelcast/internal/asyncio_connection.py im Bereich von _connect und _on_auth, reproduziere den Test unter Windows und ermittle eine stabile Lösung oder Testanpassung, die die Socket-Fehler beseitigt und die erwartete Verbindungsanzahl beibehält.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

asyncio to-jira Type: Test-Failure

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)
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
Vorherrschende Sprache
Python
Sterne
115
Forks
78
Ø Merge
2 T. 23 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus hazelcast/hazelcast-python-client

Alle Issues in hazelcast/hazelcast-python-client

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.