ProgressBar has new sysouts every line after warning.

[MrNagoo]

Current Behavior

Using a progress bar on querying data as data is actively being queried. On warning, the progressBar no longer maintains it's string replacement and instead floods the buffer.

Steps to Reproduce

1. Give Progress bar 10/10 and then hit increment
2. Change end to 11 (10/11)

Screenshot

  Querying log slices 100% [5416/5416] |================================================================================================| Time: 00:49:35
WARNING: Your progress bar is currently at 5416 out of 5416 and cannot be incremented. In v2.0.0 this will become a ProgressBar::InvalidProgressError.
Querying log slices 100% [5416/5416] |================================================================================================| Time: 00:49:37
Querying log slices  99% [5416/5418] |=============================================================================================== | Time: 00:49:37
Querying log slices  99% [5417/5418] |=============================================================================================== | Time: 00:49:38
Querying log slices  99% [5417/5420] |=============================================================================================== | Time: 00:49:43
Querying log slices  99% [5417/5420] |=============================================================================================== | Time: 00:49:43
Querying log slices  99% [5418/5420] |=============================================================================================== | Time: 00:49:44
Querying log slices  99% [5419/5420] |=============================================================================================== | Time: 00:49:45
Querying log slices  99% [5419/5420] |=============================================================================================== | Time: 00:49:45
Querying log slices 100% [5420/5420] |================================================================================================| Time: 00:49:50
Querying log slices  99% [5420/5422] |=============================================================================================== | Time: 00:49:50
Querying log slices  99% [5421/5422] |=============================================================================================== | Time: 00:49:51
Querying log slices  99% [5421/5424] |=============================================================================================== | Time: 00:49:51
Querying log slices  99% [5421/5424] |=============================================================================================== | Time: 00:49:51
Querying log slices  99% [5422/5424] |=============================================================================================== | Time: 00:49:52
Querying log slices  99% [5422/5426] |=============================================================================================== | Time: 00:49:52
Querying log slices  99% [5423/5426] |=============================================================================================== | Time: 00:49:52
Querying log slices  99% [5423/5428] |=============================================================================================== | Time: 00:49:53
Querying log slices  99% [5424/5428] |=============================================================================================== | Time: 00:49:53
Querying log slices  99% [5425/5428] |=============================================================================================== | Time: 00:49:54
Querying log slices  99% [5425/5430] |=============================================================================================== | Time: 00:49:54
Querying log slices  99% [5426/5430] |=============================================================================================== | Time: 00:49:54
Querying log slices  99% [5426/5432] |=============================================================================================== | Time: 00:49:55
Querying log slices  99% [5426/5432] |=============================================================================================== | Time: 00:49:55
Querying log slices  99% [5427/5432] |=============================================================================================== | Time: 00:49:58
Querying log slices  99% [5427/5434] |=============================================================================================== | Time: 00:49:59
Querying log slices  99% [5428/5434] |=============================================================================================== | Time: 00:50:01
Querying log slices  99% [5428/5436] |=============================================================================================== | Time: 00:50:01
Querying log slices  99% [5428/5436] |=============================================================================================== | Time: 00:50:01
Querying log slices  99% [5428/5436] |=============================================================================================== | Time: 00:50:01
Querying log slices  99% [5429/5436] |=============================================================================================== | Time: 00:50:08
Querying log slices  99% [5429/5438] |=============================================================================================== | Time: 00:50:08

And So on forever.

I'd expect after the warning to maybe create one more progress bar. As you can see cloudwatch is throwing more and more log slices into the final number.

Is this fixable?

[jfelchner]

Let me see what I can find out here for you :) It might be a couple months but I'll add it to my list.

[jfelchner]

Oh now I see what your problem is here. The bar finished. Once the current hits the total, the bar is considered "finished". So you have a couple of options here:

1. You can pass autofinish: false when you create the bar. If you're tracking time (which it doesn't appear you are), you'll need to call progressbar.finish once you know you're done for all the timers to calculate correctly.
2. You can call progressbar.resume (after you update your bar total) which will recalculate everything automatically.

I would say for what appears to be your use case, #1 would be the best option. Although to be honest it doesn't look like you really know how many items you're working with so I'm not sure a progressbar is the best use case for you in the first place.

Let me know if that solution works for you :)