Skip to content

[FIXED] Possible panic in Consumer.Fetch - #1828

Merged
piotrpio merged 1 commit into
mainfrom
fix-potential-fetch-panic
Mar 19, 2025
Merged

[FIXED] Possible panic in Consumer.Fetch#1828
piotrpio merged 1 commit into
mainfrom
fix-potential-fetch-panic

Conversation

@piotrpio

@piotrpio piotrpio commented Mar 19, 2025

Copy link
Copy Markdown
Collaborator

Resolves #1823

Signed-off-by: Piotr Piotrowski piotr@synadia.com

Signed-off-by: Piotr Piotrowski <piotr@synadia.com>
@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 84.449% (+0.02%) from 84.433%
when pulling a0b4429 on fix-potential-fetch-panic
into 8e5c8b8 on main.

@wallyqs wallyqs changed the title [FIXED] Possible panic in Conusmer.Fetch [FIXED] Possible panic in Consumer.Fetch Mar 19, 2025

@wallyqs wallyqs left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@piotrpio
piotrpio merged commit fef2dbe into main Mar 19, 2025
@piotrpio
piotrpio deleted the fix-potential-fetch-panic branch March 19, 2025 15:52
@piotrpio piotrpio mentioned this pull request Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fetch tries to access metadata after parsing error

3 participants