digital-garbageandClaude Sonnet 5
eda757e103
extensive_testing round 4 found every cap added in rounds 1-3 bounded ROW content only. A slot's id/group/node class, and project_name, were never run through any length cap -- they reach render_png as "head"/"title" block kinds, which the round-2 line-truncation loop skips entirely (it only counted kind == "row"). Worse, collect()'s row-budget check never fires for a slot with zero rows (empty inputs), so slot COUNT itself was unbounded whenever each slot carries no rows. Reproduced: 3000 slots with empty inputs and 4000-char id/group strings -- total_rows stayed at 0 the entire time, so none of the three existing caps ever engaged -- cost 193.6s render time and produced a 12.1MB embedded tEXt JSON, with zero truncation declared anywhere on the card. Fixed by: capping slot id/group/node/project_name/wired-from-label length via a new _cap() helper (same truncation as _short(), without its display-value formatting so "no id"/"no group" fallbacks still work); capping slot COUNT directly in collect() rather than relying on row count; and making render_png's line-truncation loop count "head" blocks toward the same budget as "row" blocks, as defense in depth against any other block kind reaching render with no accompanying row. Added a test reproducing the exact empty-input/huge-id shape, asserting on render_png's wall-clock time and both the PNG size and the embedded JSON size. Co-Authored-By: Claude Sonnet 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.