b6b507c48b
The auto FBCache policy keyed on the full step count whenever strength was omitted, but the loader only passes the strength kwarg when it is set, so an img2img/inpaint pipe then runs its OWN signature default (< 1, e.g. FluxImg2ImgPipeline's 0.6). FBCache would engage on the full 28 steps while the pipe actually denoises ~16, degrading the image on exactly the short trajectory the policy exists to keep uncached. Thread the pipe's signature default into the policy via a new effective_request_strength helper (unit-tested), so the effective denoise count matches what the pipe runs. |
||
|---|---|---|
| .. | ||
| assets | ||
| auth | ||
| core | ||
| hub | ||
| loggers | ||
| models | ||
| plugins | ||
| requirements | ||
| routes | ||
| state | ||
| storage | ||
| tests | ||
| utils | ||
| __init__.py | ||
| _platform_compat.py | ||
| cloudflare_tunnel.py | ||
| colab.py | ||
| main.py | ||
| run.py | ||
| startup_banner.py | ||