2 Commits

Include renames

Author	SHA1	Message	Date
chrislu	56608aead3	feat: major consumer group breakthrough - fix FindCoordinator v2 and JoinGroup v5 ... 🎉 MAJOR PROGRESS: - Fixed FindCoordinator v2 response format (added throttle_time, error_code, error_message, node_id) - Fixed JoinGroup v5 request parsing (added GroupInstanceID field parsing) - Consumer group coordination now working: FindCoordinator -> JoinGroup -> SyncGroup - Sarama consumer successfully joins group, gets member ID, calls Setup handler ✅ Working: - FindCoordinator v2: Sarama finds coordinator successfully - JoinGroup v5: Consumer joins group, gets generation 1, member ID assigned - Consumer group session setup called with generation 1 ❌ Current issue: - SyncGroup v3 parsing error: 'invalid member ID length' - Consumer has no partition assignments (Claims: map[]) - Need to fix SyncGroup parsing to complete consumer group flow Next: Fix SyncGroup v3 parsing to enable partition assignment and message consumption	2025-09-12 15:16:39 -07:00
chrislu	687eaddedd	debug: add comprehensive consumer group tests and identify FindCoordinator issue ... - Created consumer group tests for basic functionality, offset management, and rebalancing - Added debug test to isolate consumer group coordination issues - Root cause identified: Sarama repeatedly calls FindCoordinator but never progresses to JoinGroup - Issue: Connections closed after FindCoordinator, preventing coordinator protocol - Consumer group implementation exists but not being reached by Sarama clients Next: Fix coordinator connection handling to enable JoinGroup protocol	2025-09-12 15:08:55 -07:00