Force flush latest log messages before stopping the progress tracker #19
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.
Update the
ProgressTracker.stop
method to callMultiBar.update
beforeMultiBar.stop
in order to force it to flush the latest accumulated log messages right away instead of waiting for the next regular update that will never come.Manual Testing
Temporarily update
src/actions/download/downloader.ts
to usethis.progressTracker.log
instead ofprogressBar.setStatusSummary
to post its final updates:Note: not making this particular change permanent since it actually makes more sense to post this final update about having saved the last processed file name to the right of the progress bar where it normally shows the current file being copied [rather than above the progress bar].
Run the tool:
npm run build && node dist X:
, and review the output.AR == ER: the two final updates are printed above the progress line.