Unexpected std.Progress behaviour?

Help
1

Is this a bug or I am missing some option?

[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
[2/2] Processing
^C [30/120] Syncing

v0.14.0 fbsd via ghostty

PS. would adding a spinner be a good PR?

Zig's New CLI Progress Bar Explained
2

Try a recent version and see what happens.

3

I would, but I have two deps behind 0.14 so not an option at the moment. The main “stage” works fine so I thought this must be something local.

UPD: Yep, turned out a newline in the node name causing the duplicates.

4

But 0.14.1 coud/should work? This is the version with bug fixes.

5

I got it working. The issue was a newline in the node name that I needed to compensate the breaking output. But I just dropped progress defer and explicitly declared end() to avoid newline usage. Tho one might still need newlines in the node name, Ill test it later when fbsd port update is merged (there is no .14.1 binaries, just the head and 0.15).