digital-garbage
ca913a3dec
Both findings from the adversarial pass, confirmed and fixed. RESTARTING FOR NOTHING. Every successful git call scheduled a restart, whether or not the checkout had moved. Pressing Update while already up to date is a normal thing to do -- there is no way to know until it has been asked -- and it cost a full boot. The route now restarts only when something actually moved: a commit changed, or a branch did. Two branches at the same commit still count, because they stop being the same the moment anything lands on either. And the worse half, which the pass rated first: nothing checked whether a generation was in flight. The restart takes the run with it, GPU time already spent, with no warning anywhere. The window now says a run is going and turns off the three buttons that would end it. CHECK FOR UPDATES COULD NOT REPORT ONE. check_updates() answers under `checked` and the app read `nodes`. The request succeeded, the JSON was valid, and every pack reported nothing to update however far behind it was -- a fetch per pack over the network for an answer that could never be shown. Neither side's tests could see it: the route test asserted the server's shape, the window test never pressed the button, and nothing compared the two. So the tests now name each other. The Python one asserts the key the app reads; the browser one stubs the server's real shape and reads the words off the row.
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.