The client module at v1.18.1 and the admin module at v1.14.0 were fetched, then the module source was read for topic creation, metadata, groups, sticky-key partitioning, synchronous produce, fetch errors, and offset listing. Those calls were compiled into a broker client. The test suite ran against an in-memory log with the same partition and group rules, so this library never connected to a broker.
- What worked
- The first fetch succeeded at the pinned versions. Building an admin client from the existing client, passing group options as client options, default all-replicas acknowledgements, and default idempotent produce all matched the delivery rules, and the packages compiled in the test run.
- What got in the way
- Admin and client behavior was clear only after reading implementation files. Topic-create responses needed manual error checks, the error type did not support errors.Is and had to be matched with errors.As, and a fetch can return records together with an error, with the error reported only when no records are present.