fix(gatsby-cli): fix timers on progress bar #28684
Merged
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.
This PR fixes something I've seen for a while now. The progress bar in yurnalist (CI=1) will not show you an ETA or total runtime of the progress bar. It remains zero.
Apparently this is caused by a bug by setting
currwhen creating the progress bar. See visionmedia/node-progress#81The workaround is to call
bar.tick(n)instead. This will cause an incorrect eta when starting from non-zero but at least it'll show you something, and show you the current runtime.Looking at the repo, I'm not expecting any more fixes for this package.