-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version: redesign output #3499
Comments
maybe something like this yaml (btw need to look into possibly unifying analytics collection with this):
easilly greppable and json-compatible. Could also use some colors to highlight stuff |
`dvc version` output was adjusted for urgent debugging purposes and I didn't send a doc update because it is terribly ugly right now anyway. Instead, I've created iterative/dvc#3499 to tackle that, but @shcheklein reasonably requested a temporary doc update just for the sake of it, so here we go.
`dvc version` output was adjusted for urgent debugging purposes and I didn't send a doc update because it is terribly ugly right now anyway. Instead, I've created iterative/dvc#3499 to tackle that, but @shcheklein reasonably requested a temporary doc update just for the sake of it, so here we go.
Hi, Is there anyone working on this issue. if not then can I work on this issue? |
@sahilbhosale63 Sure! Let's start by discussing the output format in this ticket, so that we are on the same page and then, once we agree, we could proceed implementing it in the code. Thank you! 🙏 |
Yes, Let's start. |
Can you please provide me with the path to the file where this code resides? |
Hi @sahilbhosale63, version command is here: dvc/command/version.py. |
@sahilbhosale63, it'd be great to see example output before implementing. What do you have in mind? Also, feel free to discuss this here and/or in chat on |
Currently I don't have any ideas in my mind. I think the output format suggested by @efiop will be the best fit. And surely I will try to modify the output format and according let you know if any idea looks good to me and after that we can have a discussion. |
@sahilbhosale63 That was just a random suggestion, I admittedly didn't think about it too much. But that could be a good start and it definitely more informative than it is right now. If there are no other suggestions, please feel free to give it a shot. |
This is the change which I have made. @efiop What do you think of it? Would you like to give any suggestions on this? |
@sahilbhosale63 That looks good! Please feel free to submit a PR. Thank you! 🙏 |
@sahilbhosale63, @efiop, I think we should try making the output format human-readable rather than longer. For me, and the team, the important use case of How about something like this:
There's a room for improvement of ^ for sure. |
@skshetry Sure, that looks pretty good! @sahilbhosale63 would you be up for changing the output to that new format? |
can we do something with that ugly warning? can we embed it into the |
Here, the "Supports" and "Cache" lines highlighted in red in the above img should come in a single line under "Supports"as suggested by @skshetry. But the thing is some remotes or caches might not be supported in some systems. As in this case, reflink is not supported. So, here we can't just put the msg as "Supports: All remotes and cache types". So what should be done here? |
@sahilbhosale63, most of the times, dvc will either support all of the remotes or any one of them (two or three if there's already some dependencies installed but rare). And, Also, I'm fine with the following: # Single remote:
Supports: gs remote, and hardlink/symlink cache types
# if it supports all remotes:
Supports: All remotes and reflink/hardlink/symlink cache types
# if it supports most of the remotes, but not all, we can make it a bit ugly as it is a rare scenario:
Supports: gs, azure, hdfs, azure, oss, ssh, gdrive remotes and reflink/hardlink/symlink cache types As you can see, the last example is a bit lengthy. Also @sahilbhosale63, feel free to change the output format Thanks a lot for taking the task. 👍 |
I have made the required changes. The only think which I want to ask is there is a line break after the end of this line "Supports: All remotes" because of this line of code The code adds a line break after every sentence but I don't want a line break after "Supports: All remotes" so that the output would look like this "Supports: All remotes and hardlink/ symlink cache types" in a one single line. So is there anyway we can achieve that in python?? |
@skshetry what should we do if we can't test for link type support? I feel that we should not mix this information. Remotes are remotes, links are links - they are different, not related to each, so why do we show them in a single line? |
Redesigned the output format for the command: dvc version
…put-dvc Version: Redesign output format iterative#3499
Done some suggested fixes in code for the dvc command output format issue.
) * Version: Redesign output format #3499 Redesigned the output format for the command: dvc version * version: reformat output format #3499 Done some suggested fixes in code for the dvc command output format issue. * version: redesign output format #3499 * version: redesign output format for dvc command #3499 * version: redesign output format #3499 * version: redesign output format #3499 * Redesign output format for the dvc version command #3499 * Redesign output format for the dvc version command #3499 * Update dvc/command/version.py Co-authored-by: Saugat Pachhai <[email protected]> Co-authored-by: Ruslan Kuprieiev <[email protected]> Co-authored-by: Saugat Pachhai <[email protected]>
@efiop @sahilbhosale63 do we need to update docs? |
Yes @shcheklein, We have to update the docs. |
Current
dvc version
output is ugly, we could definitely do better:Related #3185
The text was updated successfully, but these errors were encountered: