Repository navigation
prevent ingestion stall on invalid content-length - #213
Merged
Merged
Conversation
production deployment uses scaleway's s3 offering said offering has been (very rarely) observed to corrupt objects corrupted objects can still be requested, though their purported `content-length` will be smaller than their real length this is problematic when consuming objects in a streaming-fashion, as the s3 sdk does _not like this_ ingestion ends up stalling out, as advertised `content-length` is never reached
PhilipTrauner
added a commit
that referenced
this pull request
Oct 12, 2026
handle leakage still occurs with disposal introduced in #213
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
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.
production deployment uses scaleway's s3 offering
said offering has been (very rarely) observed to corrupt objects corrupted objects can still be requested, though their purported
content-lengthwill be smaller than their real lengththis is problematic when consuming objects in a streaming-fashion, as the s3 sdk does not like this
ingestion ends up stalling out, as advertised
content-lengthis never reached