lllyasviel / lllyasviel/sd-forge-layerdiffuse
Error running process_before_every_sampling: ....... TimeoutError: [WinError 10060]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.1k
- Forks
- 352
- PR merge metrics
- No merged PRs in 30d
Description
Error running process_before_every_sampling: C:\webui_forge_cu121_torch21\webui\extensions\sd-forge-layerdiffuse\scripts\forge_layerdiffusion.py
Traceback (most recent call last):
File "urllib\request.py", line 1348, in do_open
File "http\client.py", line 1282, in request
File "http\client.py", line 1328, in _send_request
File "http\client.py", line 1277, in endheaders
File "http\client.py", line 1037, in _send_output
File "http\client.py", line 975, in send
File "http\client.py", line 1447, in connect
File "http\client.py", line 941, in connect
File "socket.py", line 845, in create_connection
File "socket.py", line 833, in create_connection
TimeoutError: [WinError 10060] 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。
what's wrong. god
Contributor guide
No contributing guide indexed for this repository
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
The traceback points to extensions/sd-forge-layerdiffuse/scripts/forge_layerdiffusion.py and Python's urllib request path. Start by reproducing the error in the reported Windows environment and inspect the network request made during process_before_every_sampling. Done means the timeout's cause is identified and the issue has a verified resolution or a documented diagnostic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100