Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Update Zeebe to 8.2.0-alpha4 #266

Merged
merged 4 commits into from
Feb 21, 2023
Merged

feat: Update Zeebe to 8.2.0-alpha4 #266

merged 4 commits into from
Feb 21, 2023

Conversation

saig0
Copy link
Collaborator

@saig0 saig0 commented Feb 21, 2023

Description

Update to the latest Zeebe alpha version 8.2.0-alpha4.

The log4j version is not compatible with slf4j 2.x. As a result, the engine produces no logs. Fixing the issue by downgrading to slf4j 1.x.
@saig0 saig0 requested a review from ChrisKujawa as a code owner February 21, 2023 04:46
@saig0 saig0 merged commit 8315b10 into main Feb 21, 2023
@saig0 saig0 deleted the update-8.2.0-alpha4 branch February 21, 2023 04:54
@saig0 saig0 mentioned this pull request Feb 21, 2023
listener: LogStorage.AppendListener
) {
try {
val entry = Entry(blockBuffer)
val copy: DirectBuffer = BufferUtil.createCopy(bufferWriter)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@saig0 why do you think this was necessary now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kept the original structure of the in-memory log storage. Since the API changed, I needed to extract the content of the BufferWriter to fill the entry.

But maybe, there is another way. I'm open to your ideas. 😄

@@ -60,7 +60,7 @@
<assertj.version>3.24.2</assertj.version>
<awaitility.version>4.2.0</awaitility.version>
<log4j.version>2.19.0</log4j.version>
<slf4j-api.version>2.0.4</slf4j-api.version>
<slf4j-api.version>1.7.36</slf4j-api.version>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😿

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤣 Yes. Log4j is not compatible yet. As a result, there were no logs printed anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants