improve human readable output#459
Conversation
67d6240 to
42238c9
Compare
|
As there is a new pre-release... Can I have a quick feedback and state on this? |
|
The current release only has bugfixes in the main code (it's only the adjunct scripts & manpages that got enhancements). I'm very cautious in making output-affecting changing, but will be giving this a closer look. |
|
I can understand you are cautious about making output-affecting changing, guess this is due to breaking scripts that expect specific output? |
|
@eworm-de could you add a description of the before and after of what this change does? Needs a bit more context than "improve" :-) |
|
The commit messages have the details. Are you missing something there or just here in the pull request? |
933dc1f to
75ea671
Compare
|
This is the output of |
0ca5744 to
6abcd9b
Compare
|
Just added another commit: |
a20c3e6 to
cb0b932
Compare
I still stand by my point: This is about human readable output. We should not be worried too much about compatibility with parsers. |
|
Any news on this? Does it help if I split this across several pull requests? |
9bcdb1b to
050399c
Compare
46d2d98 to
a5a0fa6
Compare
e05ae95 to
1b83598
Compare
steadytao
left a comment
There was a problem hiding this comment.
Thanks for sticking with this. I like the direction of making the formatter less hand-coded but I would request changes on the current patch.
Alongside my inline comments, the manpage progress examples are now stale and the current tests dont appear to cover the exact human-readable/progress output being changed here. Given this changes user-visible output, I think it needs focused formatter/progress coverage before merge alongside the bug fixes.
4b09949 to
b833d8c
Compare
steadytao
left a comment
There was a problem hiding this comment.
Quick overall thing as well as the inlines. The manpage progress examples are still stale and the tests still only check very broad output properties. Since this PR intentionally changes user-visible formatting, I think it needs very focused tests for the formatter and at least one exact progress/final-stats shape before merge.
Ups, I was not aware that the dynamic precision never made it into the man page. Updated... Is that sufficient?
Agreed. But the test suite is (mostly?) python, and I am not very familiar with that. Any help appreciated... |
ad844de to
e329ff1
Compare
|
Oh, you pushed commit into my pull request. Gladly I noticed before I force-pushed my rebase. 😄️ Some of your changes are more cleanups for my commits. Is it ok for you if I clean up the history a bit? Also some of the code is heavily influenced by you. Are you fine if I add |
Feel happy to. You can even make changes if you notice anything. It is your branch 😁
I wouldn't mind either way but thank you for the offer, of course you can! |
This drops a lot of `else if` blocks and extends units by "E" (Exa), which is 2^60 and thus the last to fit into int64. Co-authored-by: Zen Dodd <mail@steadytao.com>
Co-authored-by: Zen Dodd <mail@steadytao.com>
Let's lower precision for huge numbers. The output used to be: 3.45M -> 46.73M -> 523.11M -> 1.24G -> ... With this change the code always gives the three most significant digits: 3.45M -> 46.7M -> 523M -> 1.24G -> ... Co-authored-by: Zen Dodd <mail@steadytao.com>
... just make sure no precision is added. Co-authored-by: Zen Dodd <mail@steadytao.com>
Co-authored-by: Zen Dodd <mail@steadytao.com>
Let's also simplify the code for rate in progress, and benefit from same functionality. Co-authored-by: Zen Dodd <mail@steadytao.com>
... and also fix the formatting in man page. Co-authored-by: Zen Dodd <mail@steadytao.com>
|
Shuffled a bit... The result should be the same. Again, thanks a lot! |
|
Thank you for your work! |
Calculate in a loop, use dynamic precision.