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
What steps does it take to reproduce the issue? Uploading many files that take a while to upload and for hashes to be calculated, one can see the progress bar jump around.
**Which version of Dataverse are you using?**5.10.1
The root cause is that the code calculating the md5 hash an uploaded file is updating all progress bars instead of just it's own. This is only a problem when the bar is > 50% (the first half of the bar is the upload time, the second half is when the file is being read to calculate the local hash). It is only the hashing progress that is updating all bars instead of its own. Other bars <50% get reset whenever their thread updates the upload progress. If there is more than one file in the hash calculation stage, all bars will bounce to the progress for whichever file reports, so bars can go up/down repeatedly.
What steps does it take to reproduce the issue? Uploading many files that take a while to upload and for hashes to be calculated, one can see the progress bar jump around.
**Which version of Dataverse are you using?**5.10.1
The root cause is that the code calculating the md5 hash an uploaded file is updating all progress bars instead of just it's own. This is only a problem when the bar is > 50% (the first half of the bar is the upload time, the second half is when the file is being read to calculate the local hash). It is only the hashing progress that is updating all bars instead of its own. Other bars <50% get reset whenever their thread updates the upload progress. If there is more than one file in the hash calculation stage, all bars will bounce to the progress for whichever file reports, so bars can go up/down repeatedly.
The problem is in
dataverse/src/main/webapp/resources/js/fileupload.js
Line 321 in fdef1f6
The text was updated successfully, but these errors were encountered: