John Duffell
John Duffell
since no-one has looked at this yet, it probably won't be looked at soon
reopening as this is causing problems for users
no, sorry, as before we are working in the open so you can see and review all our code, but the configuration and other specific data is stored privately in...
Sorry, there's nothing as far as I know. Also, it has never been tested as a normal usage, so I wonder if the limitations would be too restrictive to do...
since no-one has looked at this yet, it probably won't be looked at soon
sounds better to me, although getting it from the build output would make more sense than from git directly, I'm not a big fan of automatically writing back to git...
nice idea, I also have trouble to find the source and destination without opening up all the levels.
thanks @SethTisue - I don't believe the fix has been backported to 3.3.2, I think it's likely to end up in 3.3.3 instead. I have updated the PR to 3.4.0...
this version is still vulnerable https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-6378 and 1.2.x is (edit: deprecated) https://logback.qos.ch/download.html
1.4.14 is out since december I have made a PR here which seems to pass tests OK locally: https://github.com/lightbend-labs/scala-logging/pull/432 although that PR may also have the same test failures as...