ConnectionResetError: [WinError 10054] 远程主机强迫关闭了一个现有的连接
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the issue on Windows by opening the local URL and, if relevant, the public Gradio URL shown in the report. Start with the asyncio Proactor transport traceback in the Python environment; done means browser access no longer produces the reported ConnectionResetError, with the triggering conditions documented.
Written by the indexing model from the issue text.
Description
只要浏览器访问就报错呢?
Running on local URL: http://127.0.0.1:7861
Running on public URL: https://0d49dcb5463d1abe5b.gradio.live
This share link expires in 72 hours. For free permanent hosting and GPU upgrades, run gradio deploy from Terminal to deploy to Spaces (https://huggingface.co/spaces)
ERROR:asyncio:Exception in callback _ProactorBasePipeTransport._call_connection_lost(None)
handle: <Handle _ProactorBasePipeTransport._call_connection_lost(None)>
Traceback (most recent call last):
File "D:\ProgramData\anaconda3\envs\FunClip\lib\asyncio\events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "D:\ProgramData\anaconda3\envs\FunClip\lib\asyncio\proactor_events.py", line 165, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
ConnectionResetError: [WinError 10054] 远程主机强迫关闭了一个现有的连接。
ERROR:asyncio:Exception in callback _ProactorBasePipeTransport._call_connection_lost(None)
handle: <Handle _ProactorBasePipeTransport._call_connection_lost(None)>
Traceback (most recent call last):
File "D:\ProgramData\anaconda3\envs\FunClip\lib\asyncio\events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "D:\ProgramData\anaconda3\envs\FunClip\lib\asyncio\proactor_events.py", line 165, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
ConnectionResetError: [WinError 10054] 远程主机强迫关闭了一个现有的连接。
- Dominant language
- Python
- Stars
- 6.3k
- Forks
- 753
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelscope/FunClip
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelscope/FunClip#216 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 66/100
modelscope/FunClip#215 · 3 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 76/100
modelscope/FunClip#214 · 1 comment ·
-
为什么总显示各种库未安装呢 Openneeds feedback question
Difficulty 3/5 1-2 days Newbie friendliness 35/100
modelscope/FunClip#147 · 4 comments ·
-
多人区分说话报错 Openbug needs feedback
Difficulty 3/5 1-2 days Newbie friendliness 42/100
modelscope/FunClip#139 · 6 comments ·
All issues in modelscope/FunClip
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·