Conversation
Brings back progress spinner and ETA estimate
Member
|
Do you have a commit reference for when this was removed? |
d7919
approved these changes
May 24, 2018
Member
Author
Contributor
|
Sorry my bad. Thanks for fixing! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In
Output::print, the call to flushstdoutwas accidentally clobbered. This resulted in the progress spinner and ETA estimate not getting to screen before the carriage return inBoutMonitor::call. This explicitly flushesstdoutagain to reenable the spinner/ETA.