digital-garbageandClaude Opus 5
5b21ee7c92
A malformed slots payload crashed the route with a TypeError and answered 500 in plain text. The round-two fix handled the ABSENCE of slots and not their SHAPE, so reading slot["id"] off a string went straight through -- and a refusal the app cannot parse is the failure this endpoint exists to avoid. The shape check is its own function now, because a malformed REQUEST and an unfinished PIPELINE are different things and get reported separately. And a window could still be made unreachable, by resizing rather than moving. Round two clamped position and said "a window can never be put somewhere it cannot be recovered from"; size was never bounded, so a corner drag grew it to 4937px in a 900px viewport and carried its own close and maximise buttons off the screen, leaving Escape as the only way out. Capping size to the viewport was not enough either: with x above zero the right edge still left. Resizing is now capped to the room available from where the window sits, which is a deliberately different rule from dragging -- a window may be DRAGGED partly off, because a grabbable strip is guaranteed and that is ordinary behaviour, but it may not be GROWN past the edge it is anchored to. Two rounds of fixes, two rounds of holes in those fixes. Both found only by attacking the code as it stood after the previous fix rather than stopping at the report that prompted it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.