Thanks a lot for taking the time to file this issue 🤗.
Issues do not only help to improve the library, but also publicly document common problems, questions, workflows for the whole community!
Thus, issues are of the same importance as pull requests when contributing to this library ❤️.
In order to make your issue as useful for the community as possible, let's try to stick to some simple guidelines:

• 1. Please try to be as precise and concise as possible.
     Give your issue a fitting title. Assume that someone which very limited knowledge of Diffusers can understand your issue. Add links to the source code, documentation other issues, pull requests etc...
• 2. If your issue is about something not working, always provide a reproducible code snippet. The reader should be able to reproduce your issue by only copy-pasting your code snippet into a Python shell.
     The community cannot solve your issue if it cannot reproduce it. If your bug is related to training, add your training script and make everything needed to train public. Otherwise, just add a simple Python code snippet.
• 3. Add the minimum amount of code / context that is needed to understand, reproduce your issue.
     Make the life of maintainers easy. diffusers is getting many issues every day. Make sure your issue is about one bug and one bug only. Make sure you add only the context, code needed to understand your issues - nothing more. Generally, every issue is a way of documenting this library, try to make it a good documentation entry.
• 4. For issues related to community pipelines (i.e., the pipelines located in the examples/community folder), please tag the author of the pipeline in your issue thread as those pipelines are not maintained.

For more in-detail information on how to write good issues you can have a look here.