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
If all videos have been stored on the LAN (e.g. NAS) path, but not all of those have been uploaded, it's possible for the uploader client to clear/delete its own Video Cache Record cache, so that no LAN client realizes videos still need to be uploaded.
In this state, other users can see that there are videos which they need to download, but they haven't been downloaded yet, and will show up like this under Settings > Debug tab (and issue errors in the devTools Network and perhaps console log as well):
Whenever a new client is created associated with a user who has already stored videos on the LAN, the new client can search for any video cache records on the LAN with (uploadeds) video blobs that have not been uploaded by the old client(s) and assume responsibility for uploading them after initialization.
ALTERNATIVE: Have all clients detect when there are pending uploads and join in the effort to upload them. (Not sure what will happen if we try to upload the same blob over again)
The text was updated successfully, but these errors were encountered:
If all videos have been stored on the LAN (e.g. NAS) path, but not all of those have been uploaded, it's possible for the uploader client to clear/delete its own Video Cache Record cache, so that no LAN client realizes videos still need to be uploaded.
In this state, other users can see that there are videos which they need to download, but they haven't been downloaded yet, and will show up like this under Settings > Debug tab (and issue errors in the devTools Network and perhaps console log as well):
PROPOSED solution:
Whenever a new client is created associated with a user who has already stored videos on the LAN, the new client can search for any video cache records on the LAN with (uploadeds) video blobs that have not been uploaded by the old client(s) and assume responsibility for uploading them after initialization.
ALTERNATIVE: Have all clients detect when there are pending uploads and join in the effort to upload them. (Not sure what will happen if we try to upload the same blob over again)
The text was updated successfully, but these errors were encountered: