Conversation
Signed-off-by: chlins <chlins.zhang@gmail.com>
Summary of ChangesHello @chlins, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request standardizes the display of data sizes and transfer speeds within the progress bar by switching from binary (base-1024) to decimal (base-1000) SI units. This change ensures that all reported metrics are consistent with standard SI prefixes, improving clarity and uniformity in data representation. Highlights
Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request aims to switch the progress bar display to use SI units (base-1000) instead of binary units (base-1024). While the intent is good, the implementation has a couple of issues that prevent it from working as expected.
My review points out that the usage of decor.SizeB1000(0) is incorrect and effectively results in no change from decor.SizeB1024. I've suggested using the decor.SizeB1000 constant directly.
Additionally, I've identified an inconsistency where the total size on completion would be displayed in binary units due to humanize.Bytes, contradicting the goal of the PR. I've suggested a simplification that resolves this and ensures consistent unit display throughout the progress bar's lifecycle.
This pull request makes a minor adjustment to the progress bar formatting in
internal/pb/pb.go. The change updates the units used for displaying file sizes and average speeds in the progress bar from binary (base-1024) to decimal (base-1000), ensuring consistency with other metrics.decor.SizeB1024todecor.SizeB1000for both counters and average speed decorators to use decimal units instead of binary units.