digital-garbage
ea30989752
/queue answers with queue_running AND queue_pending, and only the first was looked at. A job sits in the second from the moment /prompt returns until the worker picks it up -- always briefly, and for as long as it takes whenever something is running ahead of it, which on a shared box is the ordinary case. A reload in that window found nothing, handed Generate back, and let the same job be queued twice: the first copy then ran unnamed, its messages failing the id check, burning GPU time while the UI narrated the second. Every fixture in client.test.js was cleaner than the real payload -- none of them carried a queue_pending key at all, though ComfyUI always sends both. That is the third time a stand-in tidier than the real thing hid what it stood in for, so the fixtures now carry both halves, including the malformed entries a real answer can contain. Also renamed, because the function no longer answers the question its name asked: queuedFor returns which half it found the job in, and a job waiting its turn is adopted as QUEUED. Saying "working" over a run that has not started is the same small lie as saying "cancelled" over one that has not stopped.
ComfyUI-FunPack v5 — "Cunning Cranberry"
FunPack v4.0.0 is going to be the latest release of classic FunPack. Next update is another milestone update, or shall I say, a full rework.
Maintenance of current FunPack became a mess — forgetting to add or remove buttons from/to UI, finding functions that don't do anything but still present in the code absolutely randomly, trying to keep the UI neat while it has no strict boundaries on how it should look like, and of course — making it easy for users to understand how FunPack operates and how you can operate it — this is all time, money and token-consuming.
General idea behind the FunPack v5 rework is writing it from scratch, with a new architecture where a feature can't be forgotten, where a wire can't be missed, where one failing module never stops whole process from executing. Loaders and features would tell the UI by themselves what sorts of inputs they need and where to put it — and UI will compose them according to design guidelines it would have. Samplers would become independent from features — if a feature is available and enabled, sampler would call it. If it's not — it gets skipped and doesn't even appear in the UI so it won't confuse you.
Most of this comes from a FunUI backend draft that got shelved after understanding on how much time has to be invested into polishing it. Without a community support and wide usage it would become another dead project only one person in the world needs but no one else.
Come to think of it, FunPack already became something alike, with an exception — this project is more than alive, and while I can, I will support it.
Final goal is to make FunPack an ultimate answer for a novice's question "I don't know how to generate — what do I install and how do I start?" and for a professional's question "I need a UI with all the cutting edge techniques available on day 0 — which one?"
Preparation for the v5 had started.
FunPack v5.0 "Cunning Cranberry" — coming fall 2026.
This branch is a clean start. Classic FunPack lives on main.