lbry-desktop/static
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
..
font/v1 updates font files with normalized line height versions 2020-04-23 10:47:06 -04:00
img Add cookie spaceman to gdpr banner (#1651) 2022-06-13 15:29:13 +02:00
webworkers update webworkers 2019-11-25 11:40:19 -05:00
app-strings.json tus: don't allow 'notify' to be sent again (#1778) 2022-06-30 19:30:08 -04:00
index-electron.html Add direction 2020-07-29 17:54:10 -04:00
index-web.html MAKE ODYSEE EVEN MORE BEAUTIFUL (#539) 2022-02-11 13:50:55 -05:00
opensearch.xml Implement OpenSearch support 2020-08-12 13:35:49 -04:00
robots.txt robots.txt defaults to disallow 2020-10-12 23:33:29 -04:00