You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the process for uploading should start with a StartUploads endpoint call. My thought for this is to reset any cruft entries in the Uploads table for this client. For example, suppose that a client had to restart uploads because of a master version change. (Note that these should actually be replaced or the upload just ignored). Or suppose that a client crashed, was deleted and re-installed midway through some uploads.
Another way to deal with this might be to expire entries in the Uploads table after they've been there for a period of time.
Another way would be to have a client delete their own stale entries from Uploads.
The text was updated successfully, but these errors were encountered:
I'm attaching an example of an image that was stranded in the Shared Images Google Drive -- Haven't yet looked but I'm guessing it has an entry in the Upload table.
crspybits
changed the title
StartUploads endpoint Or expiry of Uploads entries.
StartUploads endpoint Or expiry of stale Uploads entries.
Jul 25, 2018
It seems like the process for uploading should start with a StartUploads endpoint call. My thought for this is to reset any cruft entries in the Uploads table for this client. For example, suppose that a client had to restart uploads because of a master version change. (Note that these should actually be replaced or the upload just ignored). Or suppose that a client crashed, was deleted and re-installed midway through some uploads.
Another way to deal with this might be to expire entries in the Uploads table after they've been there for a period of time.
Another way would be to have a client delete their own stale entries from Uploads.
The text was updated successfully, but these errors were encountered: