Closed Kipok closed 1 week ago
BTW another issue right now is that the download command writes a tar ball, where it may not have write permission.
Do you think a hardcoded directory, say "/workspace" might be a place where we can always write?
Well, it's a bit tricky, since we don't force users to have /workspace mount in their configs. How about instead we add a new optional argument --remote_tar_path
which can be used to specify a location on cluster/locally where to write the tar which would override the default one if present?
Cool! Let me work with that for now.
When downloading large set of metrics (e.g. majority@256), summarize_results script might work for a long time without any progress reported. Great to figure out how to print the underlying ssh logs instead or have another way to display a progress bar