d165789462
The images and video unload routes dropped their arbiter claim whenever the backend was not committed-loaded, but a concurrent /load re-acquires the owner and starts a background load that is not is_loaded for its whole download and finalize window. Releasing during that window cleared the newer load's claim, so a later chat/image load saw no owner, skipped eviction, and could allocate a second heavy model on the GPU. Gate the release on loading_repo_ids() too (both diffusion engines and the video backend expose it), not just the committed state, so an overlapping load keeps ownership. Add regression tests for the in-flight case on both routes. |
||
|---|---|---|
| .. | ||
| 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 | ||