Skip to content

Conversation

@mrnugget
Copy link
Contributor

This fixes #348 by changing the behaviour of the
progressWithStatusBarsTTY to only print status bars that have been
updated/reset.

It removes the placeholder label "Starting worker..." and simply doesn't
display status bars that don't have a value yet.

@LawnGnome can you maybe test this too? I tried to replicate different scenarios (cached, uncached, subset cached, more than numProcesses, less than numProcesses) but I'm not sure whether I caught your bug.

This fixes #348 by changing the behaviour of the
`progressWithStatusBarsTTY` to only print status bars that have been
updated/reset.

It removes the placeholder label "Starting worker..." and simply doesn't
display status bars that don't have a value yet.
@mrnugget mrnugget requested a review from a team October 14, 2020 12:48
Copy link
Contributor

@LawnGnome LawnGnome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. 👍

@mrnugget mrnugget merged commit a177c83 into main Oct 14, 2020
@mrnugget mrnugget deleted the mrn/print-only-active-bars branch October 14, 2020 17:17
scjohns pushed a commit that referenced this pull request Apr 24, 2023
This fixes #348 by changing the behaviour of the
`progressWithStatusBarsTTY` to only print status bars that have been
updated/reset.

It removes the placeholder label "Starting worker..." and simply doesn't
display status bars that don't have a value yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

campaigns: worker display is misleading if fewer workers are required than the limit

4 participants