Flaky test [Windows] ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_hostname_client_hostname [API-2340]
还没有人认领这个 Issue。
评估
调研方向
从 ReconnectWithDifferentInterfacesTest.test_connection_count_after_reconnect_with_member_hostname_client_hostname 和已链接的 Windows CI 报告开始。检查 hazelcast/internal/asyncio_connection.py 的第 576 行和第 620-624 行附近,并结合 Python 3.13 的 asyncio traceback 进行查看。当测试在 Windows 上不再间歇性失败,且其连接数断言能够稳定通过时,即表示完成。
由索引模型根据 Issue 内容生成。
描述
This test seems to fail only on Windows with Python 3.13.
Test report:
https://github.com/hazelcast/hazelcast-python-client/actions/runs/20095494138/job/57652771802#step:10:13975
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 0x000002665D6B6D70> closed. Reason: Connection closed by server
WARNING hazelcast.internal.asyncio_connection:asyncio_connection.py:581 Error during initial connection to Member [localhost]:5701 - f70c836b-be1f-4c32-acbd-49017530ceca
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
^^^^^^^^^^^^^^
- 主要语言
- Python
- 星标
- 115
- 派生
- 78
- 平均合并
- 2 天 23 小时
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
hazelcast/hazelcast-python-client 的其他 Issue
-
Type: Test-Failure
难度 2/5 1-3 小时 新手友好度 72/100
-
Type: Test-Failure
难度 3/5 1-2 天 新手友好度 52/100
-
asyncio Type: Test-Failure
难度 4/5 3-5 天 新手友好度 38/100
-
asyncio to-jira Type: Test-Failure
难度 4/5 3-5 天 新手友好度 35/100
hazelcast/hazelcast-python-client#761 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 35/100
查看 hazelcast/hazelcast-python-client 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
marketcalls/openalgo#2472 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 95/100
marimo-team/marimo#11949 ·
维护者通常 1 天内回复
-
bug server-time v2
难度 2/5 1-3 小时 新手友好度 76/100
modelcontextprotocol/servers#5559 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
jxxghp/MoviePilot#7449 ·
维护者通常 1 天内回复
-
devops help wanted
难度 2/5 1-3 小时 新手友好度 72/100
guaardvark/guaardvark#421 ·
维护者通常 2 天内回复