-
Notifications
You must be signed in to change notification settings - Fork 590
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
Enable tqdm progress in cloud environments #2698
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for investigating this @cbensimon. Solution looks ok to me 👍
Could you update this line as well please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL the nuance between disable=False and disable=None in tqdm.
same comment as @Wauplin about updating src/huggingface_hub/lfs.py#L435. Otherwise looks good to me! thanks @cbensimon!
Co-authored-by: Célina <[email protected]>
@Wauplin @hanouticelina done: src/huggingface_hub/lfs.py#L435 has been updated accordingly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @cbensimon !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @cbensimon for the PR!
Cloud environments usually enable
TQDM_POSITION=-1
to disable carriage return and get clean tqdm progress loggingThe idea of this PR is to use this environment variable as a hint to force enabling tqdm progress despite the absence of TTY
This will at least re-enable download progress in Spaces
#2000 follow-up