-
Type: Bug
-
Status: Resolved
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: 4.1.4
-
Fix Version/s: 4.4.4
-
Component/s: Remote client
-
Epic Link:
-
Tags:
-
Sprint:nxDrive 11.1.35
-
Story Points:1
Error
When resuming an upload, we first check for the batch ID validity using that pseudo-code:
try: get_batch_details(BATCHID) except Exception: log.warning("No batch ID found, restarting the upload from zero")
This is bad: we are catching all exceptions. And if the server is busy (likely when uploading a big file) it may return a HTTP error 502, 503 or 504. And those errors are not telling us that the batch ID is inexistant.
Fix
We should only catch the specific HTTP error 404.
Other errors will propagate to the upper level and will be handled accordingly.
- is related to
-
NXDRIVE-2183 Fix chunked upload using an obsolete batch ID in certain circumstances
- Resolved
-
NXDRIVE-1604 Enable to pause and resume uploads
- Resolved