Skip to content

Conversation

@NathanVss
Copy link
Contributor

@NathanVss NathanVss commented Oct 22, 2025

Fixes #348

Various fixes here.

  • Fix uploaded-ended route that could take up to a minute to resolve ( causing 502 error on ANCT instance ), it wasn't causing such issues on DINUM instance because maybe to node are bigger and because the MinIO node stands next to our app nodes, making the effect less important ).
  • Fix annoying disclaimer
  • Fix progress handler showing 100% even if the upload is not completely done. This was easy to notice on large files, amplified by the upload-ended performance issue.

@NathanVss NathanVss force-pushed the fix/upload-perf-ui branch 2 times, most recently from 9189699 to 30c8ad6 Compare October 22, 2025 13:57
@NathanVss NathanVss requested review from PanchoutNathan and lunika and removed request for lunika October 22, 2025 13:59
The previous implementation was taking a long time to read
first bytes of large files. For example it was taking 40sec
for a 750mb file. Let's use the s3 api to perform optimized
operations.
The disclaimer was always shown even if no uploads are pending.
Let's add a none state that means no uploads have been started
yet.
@NathanVss NathanVss force-pushed the fix/upload-perf-ui branch 2 times, most recently from 7a04e44 to 145de02 Compare November 6, 2025 16:04
For large uploads, the upload-ended route was still pending and
the file was displayed as "uploaded", at this point the user
could refresh its page without any disclaimer.
We want to wait for the upload-ended route to be resolved to
tell that the progress is at 100%.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upload progress bar is wrong

3 participants