huggingface / huggingface/diffusers
custom_pipeline not being cached
- Lingua principale
- Python
- Stelle
- 34.5k
- Fork
- 7.3k
- Merge medio
- 3g 3h
- PR unite (30g)
- 91
Descrizione
### Describe the bug
Components of custom pipelines (defined via custom_pipeline parameter) do not seem to be cached.
I have a multistep system where I'm loading all my components and then caching them explicitly using transformers.utils.move_cache.
I have an sdxl pipeline with `custom_pipeline="lpw_stable_diffusion_xl"`. The normal pipeline components seem to be cached correctly but not the components of the custom_pipeline.
I'm restoring the cached components by using the Pipeline with `local_files_only=True`, however diffusers is always trying to reach the internet for the custom_pipeline components, which it cannot, since the env where the restoration happens, doesn't have a connection.
### Reproduction
```python
StableDiffusionXLPipeline.from_pretrained(
"stabilityai/stable-diffusion-xl-base-1.0", torch_dtype=torch.float16,
custom_pipeline="lpw_stable_diffusion_xl"
)
```
### Logs
_No response_
### System Info
latest diffusers version from main branch
### Who can help?
@yiyixuxu @sayakpaul @DN6
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start with StableDiffusionXLPipeline.from_pretrained using custom_pipeline="lpw_stable_diffusion_xl", then inspect how transformers.utils.move_cache handles the custom pipeline components. Reproduce the restoration with local_files_only=True and verify that the custom components load from the cache without an internet connection.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- python
- Ambito
- machine-learning
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100