digital-garbageandClaude Opus 5
b3afba43e7
The claim in the last commit was too strong. Cloning stops this node touching the model everyone else holds; it does nothing about the node's own output coming back in. add_wrapper_with_key APPENDS under the key and a clone carries the list, so chaining two of these -- two passes, a flattened subgraph -- installed the same wrapper twice and ran it twice per step at double strength, while both nodes reported "1 modifier(s) applied". That is the accumulation this design is supposed to prevent, arriving through a different door. Every install is now preceded by stripping our own namespaced keys and saying how many were replaced. Foreign wrappers are never in scope, which is what the namespace was for. NaN passed validation: it compares False against both bounds, so a range check alone never fires, and json.loads accepts NaN and the infinities by default. A NaN strength reached a modifier and would have poisoned sampling with nothing reported. Non-finite numbers are now refused by name. A settings payload of the wrong shape raised AttributeError rather than the error reporting everything else here uses; the socket type is only a string match, so anything can arrive on 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.