DeFooocus_colab.ipynb Suddenly Error and Need Help
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 15/100
Rechercherichtung
Beginne mit der gemeldeten Installationsausgabe von Python 3.12 und dem Traceback durch /content/DeFooocus/entry_with_update.py, launch.py und requirements_versions.txt. Prüfe, ob der Build-Fehler von pygit2 mit diesem Repository zusammenhängt, bevor du feststellst, welche Änderung erwartet wird; als erledigt würde dies einen reproduzierbaren, repositoriespezifischen Fehler und eine definierte Behebung erfordern.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Hi,
I am new to this kind of AI tools and have 0 knowledge or experience on it before, I just find it on google and just used it for less than 1 month but it is suddenly give me error state like this:
[DeFooocus] Preparing ...
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
error: subprocess-exited-with-error
× Building wheel for pygit2 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Building wheel for pygit2 (pyproject.toml) ... error
ERROR: Failed building wheel for pygit2
error: failed-wheel-build-for-install
× Failed to build installable wheels for some pyproject.toml based projects
╰─> pygit2
/content
fatal: destination path 'DeFooocus' already exists and is not an empty directory.
/content/DeFooocus
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Installing build dependencies ... done
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
[DeFooocus] Starting ...
Already up-to-date
Update succeeded.
[System ARGV] ['entry_with_update.py', '--share', '--attention-split', '--always-high-vram', '--disable-offload-from-vram', '--all-in-fp16', '--theme', 'dark']
Python 3.12.11 (main, Jun 4 2025, 08:56:18) [GCC 11.4.0]
Fooocus version: 0.2
Error checking version for torchsde: No package metadata was found for torchsde
Installing requirements
Couldn't install requirements.
Command: "/usr/bin/python3" -m pip install -r "requirements_versions.txt" --prefer-binary
Error code: 1
stdout: Collecting torchsde==0.2.6 (from -r requirements_versions.txt (line 1))
Using cached torchsde-0.2.6-py3-none-any.whl.metadata (5.3 kB)
Collecting einops==0.4.1 (from -r requirements_versions.txt (line 2))
Using cached einops-0.4.1-py3-none-any.whl.metadata (10 kB)
Collecting transformers==4.30.2 (from -r requirements_versions.txt (line 3))
Using cached transformers-4.30.2-py3-none-any.whl.metadata (113 kB)
Collecting safetensors==0.3.1 (from -r requirements_versions.txt (line 4))
Using cached safetensors-0.3.1.tar.gz (34 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting accelerate==0.21.0 (from -r requirements_versions.txt (line 5))
Using cached accelerate-0.21.0-py3-none-any.whl.metadata (17 kB)
Collecting pyyaml==6.0 (from -r requirements_versions.txt (line 6))
Using cached PyYAML-6.0.tar.gz (124 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'error'
stderr: error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
CMD Failed requirements: install -r "requirements_versions.txt"
Total VRAM 15095 MB, total RAM 12978 MB
Forcing FP16.
Set vram state to: HIGH_VRAM
Device: cuda:0 Tesla T4 : native
VAE dtype: torch.float32
Using split optimization for cross attention
Traceback (most recent call last):
File "/content/DeFooocus/entry_with_update.py", line 46, in
from launch import *
File "/content/DeFooocus/launch.py", line 128, in
from webui import *
File "/content/DeFooocus/webui.py", line 10, in
import modules.async_worker as worker
File "/content/DeFooocus/modules/async_worker.py", line 3, in
from modules.patch import PatchSettings, patch_settings, patch_all
File "/content/DeFooocus/modules/patch.py", line 10, in
import ldm_patched.k_diffusion.sampling
File "/content/DeFooocus/ldm_patched/k_diffusion/sampling.py", line 6, in
import torchsde
ModuleNotFoundError: No module named 'torchsde'
what wrong with this? can someone help me? i already try steps from google to resolve it but is still like this. I also send email to google technical team but that is nothing until now
- Vorherrschende Sprache
- Python
- Sterne
- 1.7k
- Forks
- 408
- Ø Merge
- 2 T. 57 Min.
- Gemergte PRs (30 T.)
- 7
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus libgit2/pygit2
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 48/100
-
merge_bases not wrappedOffen
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 55/100
Ähnliche Issues
-
New InternshipOffennew_internship
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 70/100
-
[BUG] Reports tab: "Unban" button tooltip shows raw `{{ip}}` placeholder instead of the IP addressOffenbug javascript ui
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
bunkerity/bunkerweb#4001 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 92/100
PedestrianDynamics/pyFDS-Evac#476 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
google/differential-privacy#516 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
adobe-fonts/source-serif#153 ·