digital-garbageandClaude Opus 5
a81ac48083
Decode now takes the MODEL, so a provider answers "is this mine" by identity instead of by shape. H3 was claiming any latent that happened to have two parts -- right today because it is the only thing producing one, wrong the moment a second AV model exists, and wrong in the way that reads as an unrelated fault rather than an error. It declines when the model is not wired, and the node says that is what is missing. That completes the shape a model module should have: one folder saying how this model behaves at each stage -- what it is, how its latent is built, how its output is decoded -- instead of that knowledge spreading through the conditioning and sampling code as special cases. Added a modifier that runs on SD1.5, because a feature nobody can watch is a feature nobody can check. It declares no traits, so it applies everywhere, which is the other half of the rule ALG demonstrates by narrowing. Measured on this machine at a fixed seed: off and on differ, 0.4 gives a visibly richer picture that still reads correctly, and 1.2 blows the highlights -- so the range is -1..1, set from what was measured rather than from a round number. A slider whose top half destroys the image lies about its range. Two things found while building it. ComfyUI has a real circular import between nodes_latent and nodes_post_processing that resolves only because init_extra_nodes reaches one first; a custom node has to break it the same way. And the accumulation bug returned through a third door: stripping handled keyed wrappers but not the anonymous function lists on model_options, so chaining doubled the effect. Tagging is now generic -- it looks for our mark rather than for a list of hook names that would need keeping current. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
19 lines
1.0 KiB
Python
19 lines
1.0 KiB
Python
"""How a module reaches core, in both contexts, decided once.
|
|
|
|
A module cannot simply `import core`. Inside ComfyUI the pack is imported by file
|
|
location, so `core` is only reachable beneath the pack's own package; under the
|
|
tests and the dev server the repo root IS on sys.path, so it is top-level. A
|
|
static relative import gets one of those right and breaks the other.
|
|
|
|
Every module therefore imports core THROUGH here -- `from ..._core import traits`
|
|
-- and this file holds the only place that has to know about the difference. The
|
|
leading underscore keeps it out of the module scan.
|
|
"""
|
|
|
|
try: # root on sys.path: tests, dev server
|
|
from core import contract, log, patching, registry, relations, schema, traits
|
|
except ImportError: # inside ComfyUI: a subpackage of the pack
|
|
from ..core import contract, log, patching, registry, relations, schema, traits
|
|
|
|
__all__ = ["contract", "log", "patching", "registry", "relations", "schema", "traits"]
|