singularity icon indicating copy to clipboard operation
singularity copied to clipboard

Published 20 hours ago • verified publisher icon apptainer

Add ability to configure progress output frequency

Open mikegray opened this issue 5 years ago • 4 comments

Version of Singularity:

3.0.3

Expected behavior

Would like to have some progress output during push or pull, but to be able to dial back the frequency of the communication.

Actual behavior

When using push, the progress seems to be updating on the order of milliseconds which would be good for local feedback and usage for a small transfer. For a large transfer that could take minutes, I would be fine with updates every second. For a transfer that is happening from a remote build service, I do not need to be updated more than every second. Here is a log from a remote build where we end up sending a lot more information than needed across the web socket, and saving a lot more information than needed in the build log: log.txt

Steps to reproduce behavior

Execute a remote build.

mikegray avatar Jun 13 '19 14:06 mikegray

I think having a progress option for all commands would be useful. It could be hidden using --quiet.

jscook2345 avatar Jun 14 '19 02:06 jscook2345

Hello,

This is a templated response that is being sent out to all open issues. We are working hard on 'rebuilding' the Singularity community, and a major task on the agenda is finding out what issues are still outstanding.

Please consider the following:

  1. Is this issue a duplicate, or has it been fixed/implemented since being added?
  2. Is the issue still relevant to the current state of Singularity's functionality?
  3. Would you like to continue discussing this issue or feature request?

Thanks, Carter

carterpeel avatar May 15 '21 16:05 carterpeel

This issue has been automatically marked as stale because it has not had activity in over 60 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jul 14 '21 20:07 stale[bot]

@mikegray Still getting this problem ? Have this been solved already ? If yes, what work around have you followed and applied ?

We're looking into the issue carefully, soon will bring to community and discuss ways to better solve as well address this. Thankyou for keeping the interest in the subject.

pedroalvesbatista avatar Jul 15 '21 23:07 pedroalvesbatista

Transferred this issue into the new Apptainer repo https://github.com/apptainer/apptainer/issues/1161

kmuriki avatar Mar 06 '23 04:03 kmuriki