Closed galqiwi closed 2 months ago
It's not a proper fix, and I don't think that there is a proper fix. We can't know beforehand what length all these messages will have without adding unreasonable amount of complexity
@galqiwi Thanks for the PR!
Hmm, did you experience the issue with master branch? Or rather with some borg 1.2.x release (that code is in 1.2-maint branch)?
In general, the issue should first get fixed in the branch where it has been encountered and after that, it needs checking whether the other branches are affected also. Active branches are: 1.2-maint, 1.4-maint, master.
About the fix: I guess increasing by 4 instead of by 2 would cover more issues of the same kind.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 83.74%. Comparing base (
6de9ca8
) to head (e3f1349
). Report is 29 commits behind head on master.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@galqiwi did you see my feedback?
@galqiwi did you see my feedback?
Yes, sorry for late response. I've encountered this bug in 1.2.0 version. Will make a PR to the corresponding branch. By looking at the code, I see that 1.3.x and master are affected too.
OK, so now 1.2 and 1.4 branches are fixed, thanks!
You experienced the issue with 1.2.x and 1.4 is quite similar to 1.2.
OTOH, master branch has major changes, so guess one should try how it looks like there.
Also, width in this PR might need increasing (e.g. to 44), but you'll see that when practically trying it out.
Also, width in this PR might need increasing (e.g. to 44), but you'll see that when practically trying it out.
Yeah, my bad. Fixed it.
Thanks!
During
borg prune
I've encountered a minor issue -- output was not properly aligned.This PR fixes this issue. Full command with output can be viewed here.