<00:00
, add total size in bytes, etc)stage.dump
repo.check_modified_graph()
, stage.save()
, stage.dump()
etc to find out what other functions are slow, perhaps add progress for them tooExtra progress bar concern:
We started using an extra progress bar that is counting targets, as described and shown here: #2658 . In most cases though there is a single target - dvc add file
or dvc add directory
. That extra progress bar is not needed in those cases. It's needed in case of multiple targets or if -R
option is specified.
Also, when if fails to add the output is also confusing:
100%|鈻堚枅鈻堚枅鈻堚枅鈻堚枅鈻堚枅|Add 1/1 [00:02<00:00, 2.86s/file]
ERROR: output 'n01667114' does not exist
Failure or success or both?
Also on a large directory it looks like it hangs for a long time on:
0%| |Add 0/1 [00:00<?, ?file/s]
not clear what is it doing inside before running the Computing hashes
phase.
it is also stuck on that single line after the computing hashes phase.
+1 on final message and the rest.
We never had systematic approach to UI, this is the core reason of all of these.
馃挴 on We never had systematic approach to UI, this is the core reason of all of these.
馃檹
Also, it looks like on Windows dvc add
does not print anything at all for a long period of time. I don't see any progress bars whatsoever.
Created a separate ticket to deal with the missing output on Windows - #2747
Also, would probably have to add a progress bar for RemoteBase._save_dir
since it takes quite a while on dirs with giant number of files.
@efiop @casperdcl just to double check - all checkboxes are fixed in this ticket?
no it's continued in #3060
@shcheklein @efiop I think this (#2699) can be closed as #3060 mentions everything outstanding without needing to come back here for more context.
I've also checked more boxes here given #2846
Closing.