September 2022 - slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-566: Thread name possibly not populated using the fluentAPI
by QOS.CH (JIRA) 28 Sep '22

28 Sep '22

SLF4J / SLF4J-566 [Resolved] Thread name possibly not populated using the fluentAPI ============================== Here's what changed in this issue in the last few minutes. There are 2 updates, 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-566 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 28/Sep/22 12:04 PM Resolution: Not a bug Status: Resolved (was: Open) ============================== 1 comment ------------------------------ Ceki Gülcü on 28/Sep/22 12:04 PM After verification, this not an issue. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-565: Improve instructions on adding the correct combinations of dependencies
by QOS.CH (JIRA) 28 Sep '22

28 Sep '22

SLF4J / SLF4J-565 [Open] Improve instructions on adding the correct combinations of dependencies ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-565 ============================== 1 comment ------------------------------ Adam on 28/Sep/22 10:23 AM Thanks Ceki. But what are the Maven coordinates for these? Can they be listed, front and centre, like as is usual for projects? For example, # a badge that links to Maven Central [https://github.com/MicroUtils/kotlin-logging#readme] !image-2022-09-28-10-21-22-011.png|width=142,height=42! # example code with the dependencies [https://kotest.io/docs/quickstart] !image-2022-09-28-10-23-00-544.png|width=252,height=195! ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-566: Thread name possibly not populated using the fluentAPI
by QOS.CH (JIRA) 28 Sep '22

28 Sep '22

SLF4J / SLF4J-566 [Open] Thread name possibly not populated using the fluentAPI ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-566 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 28/Sep/22 9:23 AM Summary: Thread name possibly not populated using the fluentAPI Issue Type: Sub-task Assignee: SLF4J developers list Created: 28/Sep/22 9:23 AM Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-565: Improve instructions on adding the correct combinations of dependencies
by QOS.CH (JIRA) 27 Sep '22

27 Sep '22

SLF4J / SLF4J-565 [Open] Improve instructions on adding the correct combinations of dependencies ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-565 ============================== 1 comment ------------------------------ Ceki Gülcü on 27/Sep/22 7:47 PM [~adam612413213213] Which version of spring-boot are you using? ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-565: Improve instructions on adding the correct combinations of dependencies
by QOS.CH (JIRA) 27 Sep '22

27 Sep '22

SLF4J / SLF4J-565 [Open] Improve instructions on adding the correct combinations of dependencies ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-565 ============================== Issue created ------------------------------ Adam created this issue on 27/Sep/22 6:34 PM Summary: Improve instructions on adding the correct combinations of dependencies Issue Type: Improvement Assignee: SLF4J developers list Created: 27/Sep/22 6:34 PM Environment: I have recently updated Spring Boot and now I'm experience problems where the log output is not shown. In the console I see the following errors: {code:java} SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details. SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier. SLF4J: Ignoring binding found at [jar:file:/Users/semene000/.local/share/gradle/caches/modules-2/files-2.1/ch.qos.logback/logback-classic/1.2.11/4741689214e9d1e8408b206506cbe76d1c6a7d60/logback-classic-1.2.11.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation. {code} I have visited the links but they do not provide a useful explanation. I'm still not clear on what's changed, or what's wrong. The explanations seem more focused on giving context, or historical background. I'm not really interested in the history, I just want it to work. I've tried reading through the docs but they are not easy to follow. They're not clear about what artifacts are available, or where to find them. For example, when I visit most GitHub projects, one of the first things I see in the readme are instructions on how to add dependencies. Conversely, on the slf4j site I have to click around to hunt down the documentation pages. Once I find the manual https://www.slf4j.org/manual.html, it dives straight into using the code. It mentions the jars, but now where they are hosted, or the Maven coordinates. Please can you update the docs to include a clear explanation about what dependencies I should add to my Gradle project? Priority: Major Reporter: Adam ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-557: MDCCloseable: not a great fit for a try-with-resources statement
by QOS.CH (JIRA) 25 Sep '22

25 Sep '22

SLF4J / SLF4J-557 [In Progress] MDCCloseable: not a great fit for a try-with-resources statement ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-557 ============================== 1 comment ------------------------------ Alberto Scotto on 26/Sep/22 12:31 AM Yes, exactly. Your test proves my point. That is, the MDC is a concept not suited to be seen as a Closeable resource, because it leads to miss pieces of information in catch blocks. In a real world scenario, you would have: {code:java} try (MDC.MDCCloseable closeable = MDC.putCloseable(key, val)) { ... } catch (IllegalStateException e) { log.error("logging the error", e); // MDC will not be attached to this log at runtime! }{code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-557: MDCCloseable: not a great fit for a try-with-resources statement
by QOS.CH (JIRA) 25 Sep '22

25 Sep '22

SLF4J / SLF4J-557 [In Progress] MDCCloseable: not a great fit for a try-with-resources statement ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-557 ============================== 1 comment ------------------------------ Ceki Gülcü on 25/Sep/22 4:33 PM The following test fails... {code:java} public void closableTestA() { String key = "key-" + 1199; String val = "val-" + 1199; try (MDC.MDCCloseable closeable = MDC.putCloseable(key, val)) { if (1 == 1) throw new IllegalStateException("foo"); } catch (IllegalStateException e) { assertNotNull(MDC.get(key)); assertEquals(val, MDC.get(key)); } finally { } assertNull(MDC.get(key)); } {code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

slf4j 2.0.2 in the news but not on Maven Central
by Boris Unckel 23 Sep '22

23 Sep '22

Hello, slf4j 2.0.2 is in the news 2022-09-20 https://www.slf4j.org/news.html but neither announced http://mailman.qos.ch/pipermail/announce/2022/thread.html nor available (2022-09-22 16:27UTC) on https://mvnrepository.com/artifact/org.slf4j/slf4j-api Prior releases were on the same date - any issues with publishing? Regards Boris

2 2

[JIRA] Updates for SLF4J-564: SimpleLogger: handleNormalizedLoggingCall has outdated javadoc
by QOS.CH (JIRA) 21 Sep '22

21 Sep '22

SLF4J / SLF4J-564 [Resolved] SimpleLogger: handleNormalizedLoggingCall has outdated javadoc ============================== Here's what changed in this issue in the last few minutes. There are 3 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-564 ============================== 3 updates ------------------------------ Changes by Ceki Gülcü on 21/Sep/22 11:20 PM Fix Version: 2.0.3 Resolution: Fixed Status: Resolved (was: Open) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-564: SimpleLogger: handleNormalizedLoggingCall has outdated javadoc
by QOS.CH (JIRA) 21 Sep '22

21 Sep '22

SLF4J / SLF4J-564 [Open] SimpleLogger: handleNormalizedLoggingCall has outdated javadoc ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-564 ============================== 1 comment ------------------------------ Witalij Berdinskich on 21/Sep/22 10:54 PM PR#307 [slf4j-simple: fix javadoc for SimpleLogger|https://github.com/qos-ch/slf4j/pull/307] ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0