The native sd.cpp one-shot engine re-reads its companion VAE and text-encoder files from the HF cache on every generation, but the delete-cached guard only compared the loaded main diffusion repo_id. Deleting a companion repo such as comfyanonymous/flux_text_encoders while a FLUX GGUF was loaded therefore succeeded and broke the next generation. Add a loaded_repo_ids() accessor to the native backend (mirroring loading_repo_ids(), reconstructed from the committed family's VAE + text-encoder repos) and have the guard refuse those companions too. Server mode and the diffusers engine hold companions in-process/VRAM, so they are unaffected. |
||
|---|---|---|
| .. | ||
| 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 | ||