Spaces:
Running on Zero
Running on Zero
Commit History
3 days ago
-
fix: a memory refusal is its own failure category, "memory", with no GPU time used, not a bug in the app
Unverified signaturememory.MemoryPreflightError inherited the root's category, "bug", and gpu_used=True, so the session's refused run read "Something went wrong in this app — Any GPU time this run used is billed. Press Generate again." - errors.MEMORY = "memory", appended to errors.CATEGORIES after "limit" and "queue", so the existing ones keep their place: this machine's memory check declined a step and nothing was loaded for it. - MemoryPreflightError.category is "memory" and gpu_used is False. Its message is unchanged and still names LTX25_MEMORY_LIMIT_GB, the local user's knob. - Until the UI has a card for "memory", render.failure gives it the generic one ("The run did not finish", "Nothing ran. No GPU time was used."). Tests: tests/test_errors_memory.py. errors.categorise returns ("memory", False) for a refusal raised by the staged runner on the tiny checkpoint, through generate(), at each step of a run: the small set, the text encoder, the transformer, a LoRA attach, the clip encode, the …04c841e