-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic: cannot consume from pending buffer #298
Comments
@Turbo87 Which compression algorithm are you using? I suspect the decoder impl is wrong. |
zstd and gzip (see https://github.com/rust-lang/crates.io/blob/51c3f84456ecc1fc6131a1f82478536e05e4569d/crates/crates_io_cdn_logs/src/compression.rs). I just checked, we're seeing the issue for both of them apparently. |
Thanks, I will have to take a look at them. Surely I have missed something. |
Fixed #298 Signed-off-by: Jiahao XU <[email protected]>
In rust-lang/crates.io#9622 we upgraded crates.io to the latest
async-compression
release (v0.4.14), which appears to be causing issues on our staging environment:https://rust-lang.sentry.io/share/issue/9e273e28600f48a5aec2ad9e127afbbf/
The code inside the
object_store
crate is throwing a "cannot consume from pending buffer" panic, but the root cause seems to be originating from theasync-compression
crate. We use both crates roughly like this:I assume that #294 is causing this issue, but I don't know the code well enough to find the exact bug in the code changes that are causing this behavior.
The text was updated successfully, but these errors were encountered: