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
Some Spliterators have bugs in their estimateSize methods, and introducing ProgressBar can trigger these bugs when it tries to determine the initialMax value. It would be good to have ProgressBar.wrap catch any exceptions and do its best to continue. This of courses raises the question of exception logging.
Would you be open to a PR which makes this change?
The text was updated successfully, but these errors were encountered:
It sounds interesting -- how should we handle the exception? Just ignore it and continue as if it is indefinite?
This is already the behavior for InputStreams. I'll do the same for Spliterators. Thanks!
Some
Spliterator
s have bugs in theirestimateSize
methods, and introducing ProgressBar can trigger these bugs when it tries to determine the initialMax value. It would be good to haveProgressBar.wrap
catch any exceptions and do its best to continue. This of courses raises the question of exception logging.Would you be open to a PR which makes this change?
The text was updated successfully, but these errors were encountered: