Upgrading to a newer version of the segmentio/kafka-go library
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go, kafka
- Domain
- backend, distributed-systems
Research direction
Find where vroom pins segmentio/kafka-go in its Go dependency files and read the Kafka client setup. Update the dependency to version 0.4.48, then run the relevant Go checks to confirm the project builds with the newer library and supports the requested Kafka 4.0 API.
Written by the indexing model from the issue text.
Description
Hi, I’m currently in the process of migrating a self-hosted Sentry setup to kubernetes with external components, moving components out of a single Docker Compose file and into separate, independent services. One of these services is Kafka. The version of the segmentio/kafka-go library currently in use (0.4.38) does not support the new Kafka 4.0 API. Could you please update to version 0.4.48, which includes this support?
- Dominant language
- Go
- Stars
- 25
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 54
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Project submission:Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
slavakurilyak/awesome-ai-agents#845 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
JakeChampion/lang#13132 ·
Maintainers usually reply within 1 day
-
[BUG] deploy.restart_policy without condition drops the restart policyPossibly taken @akshat-lakhera claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
docker/compose#14383 · 1 comment ·
Maintainers usually reply within 1 day