build: bumped node-rdkafka from 3.1.1 to 3.2.0 #1457
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aryamohanan
commented
Nov 21, 2024
| @@ -80,7 +80,7 @@ services: | |||
| - 2181:2181 | |||
|
|
|||
| kafka: | |||
| image: wurstmeister/kafka:2.12-2.2.1 | |||
| image: wurstmeister/kafka:2.13-2.8.1 | |||
There was a problem hiding this comment.
We were using an older version of the image, but I have now updated it to the latest available version https://hub.docker.com/r/wurstmeister/kafka/tags.
aryamohanan
force-pushed
the
currency-bot-kafka
branch
from
70dfa59
to
3fb71d2
Compare
aryamohanan
force-pushed
the
currency-bot-kafka
branch
from
3fb71d2
to
8bde440
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tests were failing after upgrading node-rdkafka from v3.1.1 to v3.2.0 due to an underlying issue with librdkafka v2.6.0, which causes an error for Kafka versions earlier than 2.7.
I have raised an issue regarding this here. In the meantime, as we are using an older Kafka image version, I have updated the image to a version greater than 2.7 to work around the issue.