fix: bump tus version to resolve zero byte upload bug#1044
Merged
Conversation
ferhatelmas
approved these changes
Apr 23, 2026
Coverage Report for CI Build 24836589542Coverage decreased (-0.05%) to 69.898%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions2 previously-covered lines in 1 file lost coverage.
Coverage Stats
💛 - Coveralls |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Storage uses @tus/s3-store@2.0.2 which is has a bug that causes zero byte uploads to fail with a 500 error when using S3 backend
What is the new behavior?
Update to @tus/s3-store@2.0.3 which gracefully handles zero byte uploads to S3
Additional context
Upstream fix: tus/tus-node-server#824