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
Although the Guides say the checksum is required (see https://guides.dataverse.org/en/latest/developers/s3-direct-upload-api.html#adding-the-uploaded-file-to-the-dataset) the code doesn't do an upfront check to provide a useful 400/error message. Instead, the call eventually gets to code for the normal upload process and tries/fails to calculate the checksum on an assumed temp file copy (which doesn't exist), resulting in a failure to write a null checksum to the datafile table. The code should check for the checksum in the submitted jsonData (in the old or new format) and send a 400 error if it is missing.
Although the Guides say the checksum is required (see https://guides.dataverse.org/en/latest/developers/s3-direct-upload-api.html#adding-the-uploaded-file-to-the-dataset) the code doesn't do an upfront check to provide a useful 400/error message. Instead, the call eventually gets to code for the normal upload process and tries/fails to calculate the checksum on an assumed temp file copy (which doesn't exist), resulting in a failure to write a null checksum to the datafile table. The code should check for the checksum in the submitted jsonData (in the old or new format) and send a 400 error if it is missing.
Thanks to JHU/ @donsizemore for reporting.
What steps does it take to reproduce the issue? Call the direct upload API as in the guides but omit a checksum.
Which version of Dataverse are you using?
Dataverse 6.1 and earlier
The text was updated successfully, but these errors were encountered: