Replies: 5 comments 8 replies
-
If we had to choose one, I think I'd slightly prefer spinner |
Beta Was this translation helpful? Give feedback.
-
Added a new implementation which separated the output of progress bar into a newline @sajayantony @TerryHowe any feedback? |
Beta Was this translation helpful? Give feedback.
-
Even though it uses more vertical space, I like that implementation better than the tighter one. I like the npm style one less, but I just haven't done a lot of javascripting! |
Beta Was this translation helpful? Give feedback.
-
It might be helpful to display the time usage for uploading/downloading each blob in the progress bar. |
Beta Was this translation helpful? Give feedback.
-
The two-line one LGTM. It would be better if the cells for progress in size, %, and time are aligned. |
Beta Was this translation helpful? Give feedback.
-
Problem
As is pointed out in #940 and #893, oras commands might halt when processing data transfer tasks without any user feedback.
Solution
If ORAS user is using a terminal to run the command, we can compose an UI in the terminal and display progress status of the execution.
Goals
oras manifest fetchNon-goals
PoC
I had an implementation in my own fork based on below MVC design:
I cut three releases with different UI:
spinner: https://github.com/qweeah/oras/releases/tag/v1.2.0-spinner
progress bar: https://github.com/qweeah/oras/releases/tag/v1.2.0-bar
two-line output with progress bar: https://github.com/qweeah/oras/releases/tag/v1.2.0-2line-bar
(This implementation breaks current output style and split output of one blob into 2 lines)
To try out more commands, you may installed via below command
Beta Was this translation helpful? Give feedback.
All reactions