Progress Bars spam the terminal if the message is set too long
- Vorherrschende Sprache
- Rust
- Sterne
- 600
- Forks
- 59
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Given a single progress bar,
If a message is set to a normal length it works as intended
`filename.mp4: 18.47 MB / 41.00 MB [===>----] 45.05 % 2.35 MB/s 10s`
However if the message becomes way too long, the terminal will spam with something such as
```
[metadata] loooooooongfilename.mp4: 18.47 MB / 41.00 MB 45.05 % 2.35 MB/s 10s
[metadata] loooooooongfilename.mp4: 18.47 MB / 41.00 MB 45.06 % 2.35 MB/s 10s
[metadata] loooooooongfilename.mp4: 18.47 MB / 41.00 MB 45.07 % 2.35 MB/s 10s
[metadata] loooooooongfilename.mp4: 18.47 MB / 41.00 MB 45.08 % 2.35 MB/s 10s
[metadata] loooooooongfilename.mp4: 18.47 MB / 41.00 MB 45.09 % 2.35 MB/s 10s
[metadata] loooooooongfilename.mp4: 18.47 MB / 41.00 MB 45.10 % 2.35 MB/s 10s
```
The spam doesn't stop until the process is finished.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Look at the progress bar rendering logic, likely in a file like `src/lib.rs` or `src/progress.rs`. The issue is that long messages cause line overflow and repeated printing instead of a single updated line. Find where the bar text is formatted and written to the terminal, and check the width calculation or truncation logic. Test by creating a long filename and running a sample program to see the spam.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- cli, tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 65/100