- Added Server.GetHandler() method to expose protocol handler for testing
- Added Handler.AddTopicForTesting() method for direct topic registry access
- Fixed infinite Metadata loop by implementing proper topic creation
- Topic discovery now works: Metadata API returns existing topics correctly
- Auto-topic creation implemented in Produce API (for when we get there)
- Response sizes increased: 43→94 bytes (proper topic metadata included)
- Debug shows: 'Returning all existing topics: [direct-test-topic]' ✅
MAJOR PROGRESS: kafka-go now finds topics via Metadata API, but still loops
instead of proceeding to Produce API. Next: Fix Metadata v7 response format
to match kafka-go expectations so it proceeds to actual produce/consume.
This removes the CreateTopics v2 parsing complexity by bypassing that API
entirely and focusing on the core produce/consume workflow that matters most.
- Fixed CreateTopics v2 request parsing (was reading wrong offset)
- kafka-go uses CreateTopics v2, not v0 as we implemented
- Removed incorrect timeout field parsing for v2 format
- Topics count now parses correctly (was 1274981, now 1)
- Response size increased from 12 to 37 bytes (processing topics correctly)
- Added detailed debug logging for protocol analysis
- Added hex dump capability to analyze request structure
- Still working on v2 response format compatibility
This fixes the critical parsing bug where we were reading topics count
from inside the client ID string due to wrong v2 format assumptions.
Next: Fix v2 response format for full CreateTopics compatibility.
chrislu