lbry-desktop/web/setup
infinite-persistence 640237c630
tus: don't allow 'notify' to be sent again (#1778)
## Ticket
725

## Issue
Upload a video. When `notify` is sent at the end of the tus upload, refresh immediately. The GUI allowed the user to resume the upload, but the ID is no longer present in the server.

## Approach
Until the polling API for `notify` is available, we can only assume the best and let the user know how to handle it.
- Store the "notify was sent" state.
- Show a dialog explaining the situation.

Thought of trying to make `claim_list` calls behind the scenes to clear itself, but it doesn't handle the case of `notify` actually failing. The best is to just let the user handle it for now.

Note that for the case of `onerror` actually received, we still retry since a network error could be the culprit (`notify` wasn't sent).
2022-06-30 19:30:08 -04:00
..
publish-v1.js fix timeout with remote 2022-05-05 13:04:46 -04:00
publish-v2.js tus: don't allow 'notify' to be sent again (#1778) 2022-06-30 19:30:08 -04:00
publish.js Support stream updates via claim_id parameter (#1465) 2022-05-19 08:13:48 -04:00