Skip to content
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 #9638

Closed
sentry-io bot opened this issue Oct 12, 2024 · 1 comment · Fixed by #9639
Closed

panic: cannot consume from pending buffer #9638

sentry-io bot opened this issue Oct 12, 2024 · 1 comment · Fixed by #9639
Labels
A-backend ⚙️ C-bug 🐞 Category: unintended, undesired behavior

Comments

@sentry-io
Copy link

sentry-io bot commented Oct 12, 2024

Sentry Issue: CRATES-IO-BACKEND-3YV

panic: cannot consume from pending buffer
  ?, in rust_begin_unwind
  ?, in object_store::buffered::BufReader::consume
  ?, in async_compression::tokio::bufread::generic::decoder::Decoder<T>::poll_read
  ?, in crates_io_cdn_logs::count_downloads::{{closure}}::{{closure}}
  ?, in tracing::instrument::Instrumented<T>::poll
...
(16 additional frame(s) were not displayed)
@sentry-io sentry-io bot added A-backend ⚙️ C-bug 🐞 Category: unintended, undesired behavior labels Oct 12, 2024
@Turbo87
Copy link
Member

Turbo87 commented Oct 12, 2024

first up: this has only been panicking on our staging environment, not on production.

Sentry pointed out that 00b5b2e (aka. #9622) was the first release that saw this behavior, and since async_compression is involved in the stacktrace that seems like a very likely root cause.

I've opened Nullus157/async-compression#298 with a couple more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ C-bug 🐞 Category: unintended, undesired behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant