modelscope / modelscope/FunClip
ConnectionResetError: [WinError 10054] 远程主机强迫关闭了一个现有的连接
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.3k
- Forks
- 753
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 8
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] 远程主机强迫关闭了一个现有的连接。
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.
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.
Assessment
- Tech stack
- python
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100