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

Bump logback-classic to 1.4.14 #1291

Closed
wants to merge 1 commit into from
Closed

Bump logback-classic to 1.4.14 #1291

wants to merge 1 commit into from

Conversation

AshCorr
Copy link
Member

@AshCorr AshCorr commented Dec 12, 2023

What does this change?

Bumps logback-classic to 1.4.14. Resolving 4 high vulnerabilities.

@@ -36,7 +36,7 @@ object Dependencies {
val magentaLibDeps =
commonDeps ++ jacksonOverrides ++ akkaSerializationJacksonOverrides ++ Seq(
"com.squareup.okhttp3" % "okhttp" % "4.12.0",
"ch.qos.logback" % "logback-classic" % "1.4.8", // scala-steward:off
"ch.qos.logback" % "logback-classic" % "1.4.14", // scala-steward:off
Copy link
Member

Choose a reason for hiding this comment

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

We previously experienced an issue updating this dependency in this repository - #1232. Have we successfully deployed to CODE?

Copy link
Member Author

Choose a reason for hiding this comment

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

Haven't tried this in code. The error does seem unrelated though

java.lang.AssertionError: assertion failed: no symbol could be loaded from interface software.amazon.awssdk.services.s3.model.ListObjectsV2Response$Builder in class ListObjectsV2Response with name Builder and classloader sbt.internal.LayeredClassLoader@6286d22d

Copy link
Member Author

Choose a reason for hiding this comment

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

Yea builds now, just a fragile test. Ill give it a go in CODE tomorrow just on case though.

Copy link
Member Author

Choose a reason for hiding this comment

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

You are absolutely right this does break CODE. Unfortunately I don't think we can just dump logback and switch to devx-logs... As far as I understand Logback is pretty core to Play logging, and you would still need to use it regardless of logging to kinesis or logging to stdout 🤔

Copy link
Member

Choose a reason for hiding this comment

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

#1292 switches to devx-logs, it might not resolve the reported vulnerabilities, but it's less code in the repository 😄.

@AshCorr
Copy link
Member Author

AshCorr commented Dec 14, 2023

This version of logback-classic is incompatible with our Play version. We probably need to do a bit of work to try and get riff-raff to Play 3.0 (or atleast a newer version of play) before we can fix this vuln.

@AshCorr AshCorr closed this Dec 14, 2023
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