CLI/web upload may return 500 error even when blob appears later #31
Description
Summary
During testing on shelbynet, file uploads sometimes return a 500 Internal Server Error in the CLI and also appear to error in the web interface, but the blob can still appear later in the Shelby interface.
Environment
- CLI version: 0.0.26
- Environment: WSL / Ubuntu
- Network: shelbynet
Observed behavior
shelby uploadstarts normally- filelist is created
- upload reaches multipart stage
- CLI returns:
Failed to complete multipart upload! status: 500, body: Internal Server Error
However, in some cases the uploaded file later appears in the Shelby web interface.
The same general behavior was also observed from the web uploader:
- the interface reported an error
- but the file still appeared uploaded afterwards
Expected behavior
If the blob is successfully created, the CLI and web interface should return a success response instead of a 500 error.
If the upload truly fails, the error should clearly indicate that no blob was created.
Why this matters
This makes automation difficult, because the client may interpret the upload as failed and retry unnecessarily, even when the blob may already exist.
Suggestion
It would help if the final upload response were made more consistent, or if the CLI exposed a more reliable post-upload verification flow.