-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible to Disable/Control Progress Bars (TQDM)? #137
Comments
I was able to disable the progress produced by the guided-diffusion library through a monkey-patched hack:
This succeeds at removing the progress bars. A cleaner way would be to accept an environment variable, perhaps here: runner.py#373
Apparently this does not solve my problem, however! I am seeing a lot of newlines being generated but I am not sure where they are coming from, and this is not an issue when I am running it interactively. Odd behavior! |
For reference, this is the output in the logging file that I am seeing:
|
Yes it would be great to kill the TQDM/progress bar stuff for integration use cases. |
from 0.11.2 set env btw, we are K8s and cloud-native expert, more expert than diffusion 😉 , if you encounter any problem when deploying DiscoArt in production env such as K8s, please let us know @kevinjdolan FYI @jina-ai/engineering |
I was trying to search through the code to figure out where the progress bars are being generated, but I could not locate them. I assume they are being powered by TQDM.
I am getting frustrating output when the logs are output to a file in the context of a Docker container running on Kubernetes. I would like to either remove the TQDM rendering altogether, or modify so that it is not producing the input characters intended for a live console.
Is there a documented way to control the TQDM rendering? If not, can you point me in the right direction for how to control these?
The text was updated successfully, but these errors were encountered: