dandi / dandi/dandi-cli

Queue up assets "for later" if needing some wait time to become upload-able

Open
#942 0 comments 0 reactions 1 assignee Assigned to @yarikoptic-gitmate View on GitHub
UX
Dominant language
Python
Stars
28
Forks
37
Avg merge
1d 17h
Merged PRs (30d)
9

Description

In #930 @dchiquito suggests to address legit UX aspect that canceling of zarr upload might take awhile and thus before attempting the next one, we might need to wait.

Ideally `upload` process, while performing uploads (not while canceling them), should skip assets which aren't yet ready to be uploaded (e.g. not ready on the server side as in this case) and come back to them later. This way

- `upload` process wouldn't get stuck waiting for some asset to finally start/finish uploading
- proceed with upload of other assets
- we can interrupt upload process quickly and fire up a new upload process which would auto-magically wait if needed for upload to finally commence

so, `upload` should
- skip uploads which can't be uploaded for a reason now and should be retried later
- whenever "upload queue" has only assets being waited for -- sense if they could be uploaded "now".
- set some period of time (e.g. a minute) an asset shouldn't be tested to be reuploaded
- if no asset satisfy "retry" -- sleep until an asset could be retried an upload

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.