fix: guard TopicPartitionList capacity#836
Open
Sieger9303 wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Fixes #826.
Hi, thanks for maintaining this crate.
TopicPartitionList::with_capacityaccepts ausize, but the underlying librdkafka API takes the capacity as ani32. Previously, values larger thani32::MAXwere silently narrowed withcapacity as i32, which could lead to surprising behavior, including very large allocation attempts for some inputs.This PR adds an explicit upper-bound check before the cast and documents the panic condition. This keeps the existing API unchanged while making oversized capacities fail predictably in Rust before calling into librdkafka.