haubur opened a new issue, #3910: URL: https://github.com/apache/iggy/issues/3910
### Bug description **Description** When calling shutdown() on the IggyConsumer polling is still possible with next() but causes unintended behavior for: 1. standalone consumer next() still consumes messages from buffer or server, while sending offsets is prevented due to dropping the channel in shutdown() 2. a consumer group member after shutdown can still call next but hangs indefinitely: https://github.com/apache/iggy/blob/6043d194000cff5f5498a91dc2259e34762f7d1c/core/sdk/src/clients/consumer.rs#L695 Calling init() again is idempotent, so a user cannot recover from this state. **Options** - make poll_next() check shutdown() and return - `None` to respect the Stream trait - `IggyError` that can be handled by the user (preferred) ### Affected area / component Rust SDK ### Deployment None ### Versions _No response_ ### Hardware / environment _No response_ ### Sample code _No response_ ### Logs _No response_ ### Iggy server config _No response_ ### Reproduction _No response_ ### Contribution - [x] I'm willing to submit a pull request to fix this bug ### Good first issue - [ ] I think this could be a good first issue for a new contributor -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
