Neil Botelho
Neil Botelho
Seems like the artifacts stop if you set it to invisible before stopping it: ```python progress.update(task_id, visible=False) progress.stop_task(task_id) ```
In case you don't need all the progress bars to stay together, consider creating a new progress bar at the start of each loop instead of adding all the tasks...
It seems like this is caused by the fact that when you run a python script in jupyter like `!python script.py` it starts a separate python session without any of...
What I'm unsure of is why this works with a single task but breaks for mutliple, even when they are sequential and the progress bars are transient.
> Those commands are coming soon. Nice! Is there a tracking issue with things we can help out with?
The latest commit (390fd51) addresses the previously mentioned potential issues. The goal was to maintain the existing behavior for sequential downloads while updating the behavior of the progress bar specifically...
Thanks for catching that. Thanks to that I also noticed I hadn't handled the -q flag yet. Most of this issue is related to changes on the [rough merge of...
I wanted to gently nudge this PR for a bit more attention :) , and put forward a plan for merging this feature that hopefully makes sense. This PR adds...
Shouldn't be too difficult, it doesn't seem like #12586 adds any conflicting changes. I think a merge with main could work here?
Taking a closer look at it, I realize what you mean. I'll look into how to support the flow for simple progress bars with the changes suggested by this PR....