{"slug": "spaces-aren-t-allocating-for-zerogpu-tonight", "title": "Spaces aren't allocating for ZeroGPU tonight", "summary": "Hugging Face user AbstractPhil reports that their ZeroGPU Space 'AbstractPhil/alephllm-chat' builds successfully but never receives a hardware allocation, with the runtime API showing 'hardware.current: null' indefinitely since August 14, 2026. The issue also affects a predecessor Space, 'AbstractPhil/alephllm-chat2', which remains stuck with a hardware assignment it was asked to release. The user seeks an explanation and a fix from Hugging Face.", "body_md": "Space never allocated: `hardware.current: null`\n\n, builds succeed, app never runs\n\nClaude wrote this up to save some time. Been a bit of a journey tonight trying to get it working, so far no dice.\n\n**Space:** `AbstractPhil/alephllm-chat`\n\n(Gradio SDK, ZeroGPU requested)\n\n**Account:** AbstractPhil · **Observed:** 2026-08-14 → 2026-08-15\n\nSymptom\n\nThe Space builds successfully on every commit and is never allocated a\n\nmachine. Runtime API reports:\n\n```\nstage    : APP_STARTING        (indefinitely)\nhardware : {\"current\": null, \"requested\": \"zero-a10g\"}\nerrorMessage : null\n```\n\n`current: null`\n\npersists for hours. Switching the request to `cpu-basic`\n\ndoes not allocate either, so this is not ZeroGPU-specific.\n\nBuild is not the problem\n\nBuild log completes normally every time:\n\n``` php\n--> RUN --mount=target=/tmp/requirements.txt ... CACHED\n--> COPY --link --chown=1000 ./ /home/user/app   DONE\n--> Pushing image                                 DONE 0.8s\n--> Exporting cache                               DONE 0.5s\n```\n\nThe app is not the problem\n\nThe identical `app.py`\n\nruns correctly outside Spaces (same Python 3.12,\n\nsame gradio, same `spaces`\n\npackage): it boots, serves `/config`\n\n, and\n\nanswers requests. It is the canonical ZeroGPU shape — model loaded at\n\nmodule level and moved to `cuda`\n\n, `@spaces.GPU`\n\non the generator, plain\n\n`demo.launch()`\n\n. No threads, no locks, no asyncio, no coroutines, no\n\nsubprocesses of our own.\n\nRelated history on this account (may be the same underlying issue)\n\n-\nThe predecessor Space (now `AbstractPhil/alephllm-chat2`\n\n) spent ~16h\n\nserving a **two-day-old commit**: new builds succeeded, containers\n\nbooted cleanly with `Running on local URL`\n\n, but traffic kept going to\n\nthe old revision and `runtime.sha`\n\nnever advanced. Factory rebuild and\n\nrestart had no effect. Recreating the Space under a new name worked\n\nonce, then the new Space hit the `current: null`\n\nstate described above.\n\n-\n`alephllm-chat2`\n\nis now **PAUSED but still reports**\n\n`hardware.current: zero-a10g`\n\n, with `requested: cpu-basic`\n\nstuck in\n\nflight. Re-issuing the hardware change and restarting the Space does\n\nnot apply it. It appears to be holding a hardware assignment it was\n\nasked to release.\n\nSimilar reports\n\nAsk\n\n- Why is no machine being allocated for\n`AbstractPhil/alephllm-chat`\n\ndespite a successful build and a pending hardware request?\n- Can the stuck hardware assignment on\n`AbstractPhil/alephllm-chat2`\n\n(`current: zero-a10g`\n\nwhile PAUSED, `requested: cpu-basic`\n\n) be\n\nreleased?\n\nAdditionally, what is this TWO LINKS PER POST thing for new users? I’m nowhere near a new user for huggingface.\n\nWell on the plus side, the AlephLLM Mini-Beatrix is perfectly playable on cpu. Pretty fun ByteLM structured system turned out pretty smart.", "url": "https://wpnews.pro/news/spaces-aren-t-allocating-for-zerogpu-tonight", "canonical_source": "https://discuss.huggingface.co/t/spaces-arent-allocating-for-zerogpu-tonight/178683#post_3", "published_at": "2026-08-15 03:08:12+00:00", "updated_at": "2026-08-15 03:11:15.307890+00:00", "lang": "en", "topics": ["ai-infrastructure"], "entities": ["Hugging Face", "AbstractPhil", "AbstractPhil/alephllm-chat", "AbstractPhil/alephllm-chat2", "ZeroGPU", "Gradio", "AlephLLM Mini-Beatrix"], "alternates": {"html": "https://wpnews.pro/news/spaces-aren-t-allocating-for-zerogpu-tonight", "markdown": "https://wpnews.pro/news/spaces-aren-t-allocating-for-zerogpu-tonight.md", "text": "https://wpnews.pro/news/spaces-aren-t-allocating-for-zerogpu-tonight.txt", "jsonld": "https://wpnews.pro/news/spaces-aren-t-allocating-for-zerogpu-tonight.jsonld"}}