-
Notifications
You must be signed in to change notification settings - Fork 252
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
Dead lock if adding the same ProgressBar to MultiProgress more than once #503
Comments
Like the documentation says, a |
I'm a little unclear on why this makes us crash? It seems like it might be reasonable to, on In principle I agree that it is the caller's error, but if we can't make it statically impossible (which in this case isn't really possible) it would be nice if at least we make it error in a less painful and/or more obvious way. |
The hang occurs because Lines 135 to 141 in 98ae38d
but so does Lines 178 to 183 in 98ae38d
I can make this a no-op by adding I can't think of any reason why someone would want to do this purposely, so I'm leaning towards making it panic. Any thoughts? |
I mean, if there are no ill effects of doing so than making it a no-op seems better than making it panic. Why crash someone's program if we don't need to? |
OK, that's fair. I will make the change and add some documentation for the behavior. |
Also add some documentation
Build pass but dead lock while running. Tested with
indicatif == 0.17.2
.Output while running:
The text was updated successfully, but these errors were encountered: