You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if I don't call progress.reset() explicitly, the task2 bar will be stuck on a completed state after the first inner loop iteration, a look at the code shows that calling progress.track() on a existing task only updates the total:
so my question is, is there a use case for not reseting the task on progress.track() ? otherwise wouldn't it be better to call reset there instead of update ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, thanks for this great library, consider the following code:
if I don't call progress.reset() explicitly, the task2 bar will be stuck on a completed state after the first inner loop iteration, a look at the code shows that calling progress.track() on a existing task only updates the total:
rich/rich/progress.py
Line 1203 in 2c93dce
so my question is, is there a use case for not reseting the task on progress.track() ? otherwise wouldn't it be better to call reset there instead of update ?
Beta Was this translation helpful? Give feedback.
All reactions