Spaces:
Running
Running
Commit History
-
Stop re-resolving the spaCy model wheels on every container start Running
AgentThe Space has been stuck in RUNTIME_ERROR ("Launch timed out, workload was not healthy after 30 min") since ca0f322, with a run log containing the startup banner and nothing else. CMD is `uv run`, which re-syncs before executing. en-core-web-md and ja-core-news-md are pinned to github.com release URLs, and uv re-fetches a direct-URL wheel to generate its metadata rather than trusting the venv that `uv sync --locked` already built. Every start therefore blocks on two github.com downloads before marimo binds 7860. Reproduced by running the image with --network none: it fails in seconds with "Failed to generate package metadata for en-core-web-md ... dns error" and never starts marimo. On the Space the same request stalls instead of failing, which is why the log goes quiet for 30 minutes. With UV_NO_SYNC=1 the same --network none run prints the marimo banner and serves; with network it answers 200 in about 10 seconds and both models load inside the container.3a180ca
-
chore: update dockerfile and deps
Bor Hodoščekca0f322
-
fix: dunno (4)
Bor HodoščekUnverified signature8bfa6b3 -
fix: dunno (3)
Bor HodoščekUnverified signature83507af -
chore: update readme and reorder dockerfile
Bor HodoščekUnverified signature087a354 -
fix: dunno (2)
Bor HodoščekUnverified signaturec8903d3 -
fix: dunno
Bor HodoščekUnverified signature49dec7c -
fix: update uv and run command
Bor HodoščekUnverified signature8f1696c
-
feat: fix dockerfile
Bor HodoščekUnverified signature4d52104 -
chore: update uv & move to pyproject.toml
Verified signature75e7ffd
-
Update Dockerfile to include code by default.
Verified signatureOne of the benefits of marimo is that you can make awesome apps with little code. This change helps highlight that.b6f407d
-
Create template
4545835
