Feature #17936
closed
Arv-put resume cache handling when having expired block signatures
Added by Lucas Di Pentima over 3 years ago.
Updated over 3 years ago.
Release relationship:
Auto
Description
With the recently added token expiration features, arv-put
will start to complain more often about its resume cache not being valid anymore. In addition to this, arv-put
is called from other Arvados tools like arv-keepdocker
that may show arv-put
's suggestions to users making the UX somewhat confusing.
It may be necessary to make arv-put
automatically handle these situations, for example by removing the resume cache if it detects that there're expired block signatures on it.
Add a --batch mode to arv-put which automatically deletes the cache and retries on error.
Modify arv-keepdocker to use the --batch mode when it invokes arv-put.
- Target version changed from 2021-08-18 sprint to 2021-09-01 sprint
- Target version changed from 2021-09-01 sprint to 2021-08-18 sprint
- Description updated (diff)
- Assigned To set to Lucas Di Pentima
- Status changed from New to In Progress
Updates at 8cb640565 - branch 17936-arvput-batch-mode
Test run: developer-run-tests: #2626
- Adds
--batch
argument to arv-put
making it ignore the cache file if it's not valid.
- Makes
arv-keepdocker
to always call arv-put
with --batch
so that users don't get confusing messages regarding invalid cached signatures from an indirectly called arv-put
.
- Adds tests.
Lucas Di Pentima wrote:
Updates at 8cb640565 - branch 17936-arvput-batch-mode
Test run: developer-run-tests: #2626
- Adds
--batch
argument to arv-put
making it ignore the cache file if it's not valid.
- Makes
arv-keepdocker
to always call arv-put
with --batch
so that users don't get confusing messages regarding invalid cached signatures from an indirectly called arv-put
.
- Adds tests.
This LGTM.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF