- slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-552: Disable pattern programatically in current thread.
by QOS.CH (JIRA) 28 Jun '22

28 Jun '22

SLF4J / SLF4J-552 [Closed] Disable pattern programatically in current thread. ============================== 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-552 ============================== 1 comment ------------------------------ Martin on 28/Jun/22 9:13 PM For other people that need this, below is my solution. This will create only one event until the MDC is removed. This gives the possibility to make it dynamic within the code. I know, there is a risk to loose logs but this is only for development. I was able to do it with Custom CompositeConverter and MDC. {code:java} public class CompactDebugLoggingConverter extends CompositeConverter<ILoggingEvent> implements CompactLoggingManager { private final StringBuilder buffer =new StringBuilder(); @Override public String convert(ILoggingEvent event) { if (event.getMDCPropertyMap().containsKey(COMPACT_MSG) && event.getLevel().equals(Level.DEBUG) && event.getThrowableProxy() == null) { boolean startBuffering = buffer.length() == 0; if(startBuffering){ buffer.append(super.convert(event)); } else { buffer.append(event.getFormattedMessage()).append('\n'); } return ""; } else { String message= buffer.append(super.convert(event)).toString(); buffer.setLength(0); return message; } } @Override protected String transform(ILoggingEvent event, String in) { return in; } } {code} {code:xml} <conversionRule conversionWord="compactMsg" converterClass="log.converter.CompactDebugLoggingConverter"/> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%compactMsg(%d{yyyy-MM-dd HH:mm:ss.SSS} ${LOG_LEVEL_PATTERN:-%5p} --- [%8.8t] %-40.40logger{39} : %msg%n) </pattern> <charset>utf8</charset> </encoder> </appender> {code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-552: Disable pattern programatically in current thread.
by QOS.CH (JIRA) 28 Jun '22

28 Jun '22

SLF4J / SLF4J-552 [Closed] Disable pattern programatically in current thread. ============================== 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-552 ============================== 1 comment ------------------------------ Martin on 28/Jun/22 4:46 PM Thanks for the documentation reference, I'll try it out. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-552: Disable pattern programatically in current thread.
by QOS.CH (JIRA) 28 Jun '22

28 Jun '22

SLF4J / SLF4J-552 [Open] Disable pattern programatically in current thread. ============================== 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-552 ============================== 1 comment ------------------------------ Ceki Gülcü on 28/Jun/22 2:28 PM You may implement this functionality with custom conversion specifiers. See https://logback.qos.ch/manual/layouts.html#customConversionSpecifier Having said this, I don't think this functionality has widespread appeal. Closing. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-552: Disable pattern programatically in current thread.
by QOS.CH (JIRA) 13 Jun '22

13 Jun '22

SLF4J / SLF4J-552 [Open] Disable pattern programatically in current thread. ============================== 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-552 ============================== Issue created ------------------------------ Martin created this issue on 13/Jun/22 2:24 PM Summary: Disable pattern programatically in current thread. Issue Type: New Feature Assignee: SLF4J developers list Components: slf4j-simple Created: 13/Jun/22 2:24 PM Priority: Minor Reporter: Martin Severity: enhancement Description: Working with logger is essential for troubleshooting but sometime there is way too much debug logs. Sometime they are too verbose but still needed. I came across a issue with disk spaces and the logs were top blame. I want to propose a simple feature to the logger. Sadly I do not know who is in the top of the pyramide. Slf4j seem to be the place to begin with. Let say I have a really fast and verbose thread algorithm. {code:java} 2022-06-10 14:27:23:123 -0400 [normal] DEBUG org.slf4j.impl.App - Calling internal process 2022-06-10 14:27:23:123 -0400 [normal] DEBUG org.slf4j.impl.App - Clean up list from empty or null string 2022-06-10 14:27:23:123 -0400 [normal] DEBUG org.slf4j.impl.App - Removing : "" 2022-06-10 14:27:23:123 -0400 [normal] DEBUG org.slf4j.impl.App - Removing : "null" <...> 2022-06-10 14:27:23:123 -0400 [normal] INFO org.slf4j.impl.App - Listing entries 2022-06-10 14:27:23:124 -0400 [compact] DEBUG org.slf4j.impl.App - Return to Normal log {code} I propose to include a flag that will keep the logging and avoid duplicated the pattern. I want to: Use ThreadLocal to avoid impacting all the other logs. Enable programmatically to be specific for known verbose path only Keep the initial pattern of the first log call. Enable it only for debug level, other level will continue to be log with the pattern. Closable to be easy to use. Result must be something like this: {code:java} 2022-06-10 14:27:23:119 -0400 [compact] INFO org.slf4j.impl.App - Enabling compact logging 2022-06-10 14:27:23:120 -0400 [compact] INFO org.slf4j.impl.App - Listing entries 2022-06-10 14:27:23:120 -0400 [compact] DEBUG org.slf4j.impl.App - Calling internal process Clean up list from empty or null string Removing : "" Removing : "null" <...> 2022-06-10 14:27:23:120 -0400 [compact] DEBUG org.slf4j.impl.App - Return to Normal log {code} The code will be use like this: {code:java} @Slf4j public class App { public void publicCall( List<String> list ) { log.info("Enabling compact logging"); try (AutoCloseable ignored = ((CompactLogger)log).beginCompactLogging()) { processList(list); } catch (Exception e) { log.error("Process issue", e); } log.debug("Return to Normal log"); } } {code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-551: broken link https://github.com/qos-ch/slf4j/blob/master/slf4j-site/src/site/pages/templates/left.js#L22
by QOS.CH (JIRA) 08 Jun '22

08 Jun '22

SLF4J / SLF4J-551 [Resolved] broken link https://github.com/qos-ch/slf4j/blob/master/slf4j-site/src/site/pages/templ… ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-551 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 08/Jun/22 3:39 PM 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-551: broken link https://github.com/qos-ch/slf4j/blob/master/slf4j-site/src/site/pages/templates/left.js#L22
by QOS.CH (JIRA) 08 Jun '22

08 Jun '22

SLF4J / SLF4J-551 [Open] broken link https://github.com/qos-ch/slf4j/blob/master/slf4j-site/src/site/pages/templ… ============================== Here's what changed in this issue in the last few minutes. This issue has been created There is 1 comment. This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-551 ============================== Issue created ------------------------------ Chad K Bisk created this issue on 08/Jun/22 5:29 AM Summary: broken link https://github.com/qos-ch/slf4j/blob/master/slf4j-site/src/site/pages/templ… Issue Type: Bug Affects Versions: 2.0.0-alpha7 Assignee: SLF4J developers list Components: Unspecified Created: 08/Jun/22 5:29 AM Environment: [https://www.slf4j.org/] and most sub pages Priority: Minor Reporter: Chad K Bisk Severity: normal Description: [https://github.com/qos-ch/slf4j/blob/master/slf4j-site/src/site/pages/templ…] should probably be api/org, not org/org broken in [https://github.com/qos-ch/slf4j/commit/16ab482cab7e8fdc6468ce7da425f10660bf…] reproduce by clicking on "Log4j" link on the left navigation panel. also: you should add a slf4j-site Component to this jira ============================== 1 comment ------------------------------ Chad K Bisk on 08/Jun/22 5:32 AM https://github.com/qos-ch/slf4j/pull/290 ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-550: JPMS 下 java.lang.ClassLoader#getResource 工作差异
by QOS.CH (JIRA) 26 May '22

26 May '22

SLF4J / SLF4J-550 JPMS 下 java.lang.ClassLoader#getResource 工作差异 ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. This issue has been deleted ============================== Issue created ------------------------------ 琉璃 created this issue on 26/May/22 7:57 PM Summary: JSPM 下 java.lang.ClassLoader#getResource 工作差异 Issue Type: Story Affects Versions: 2.0.0-alpha7 Assignee: SLF4J developers list Attachments: 2022-05-27_01-55-40.jpg Components: slf4j-simple Created: 26/May/22 7:57 PM Environment: 版本 Windows 11 专业版版本 21H2 安装日期 ‎2021-‎10-‎15 操作系统版本 22000.675 java 17 2021-09-14 LTS Java(TM) SE Runtime Environment (build 17+35-LTS-2724) Java HotSpot(TM) 64-Bit Server VM (build 17+35-LTS-2724, mixed mode, sharing) Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) Maven home: C:\usr\tool\apache-maven-3.8.4 Java version: 17, vendor: Oracle Corporation, runtime: C:\usr\lib\jdk-17 Default locale: zh_CN, platform encoding: GBK OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>2.0.0-alpha7</version> </dependency> Priority: Major Reporter: 琉璃 Description: 有如下简单测试代码: There are the following simple test codes: {code:java} package cn.test.resources; import java.net.URL; public class Main { public static void main(String[] args) { URL resource = Main.class.getClassLoader().getResource(""); System.out.println(resource.getFile()); } } {code} 这是一个 maven 项目, 只有这一个文件, pom 文件仅包含 `slf4j-api` 的依赖. 如果不添加 `module-info.java` 文件, 在我的计算机上, 上述代码输出: {color:#c1c7d0}/C:/test/testJpmsResource/target/classes/{color} 如果添加了 `module-info.java` 文件, 即使没有声明 `requires org.slf4j` 我会得到下面的结果: {color:#c1c7d0}file:/C:/usr/data/maven/org/slf4j/slf4j-api/2.0.0-alpha7/slf4j-api-2.0.0-alpha7.jar!/META-INF/versions/9/{color} This is a maven project. There is only one file. The POM file only contains the dependencies of 'slf4j API' If you don't add ` module info Java file, on my computer, the above code output: {color:#c1c7d0}/C:/test/testJpmsResource/target/classes/{color} If you add ` module info Java file, even if it does not declare 'requires org Slf4j ` I will get the following results: {color:#c1c7d0}file:/C:/usr/data/maven/org/slf4j/slf4j-api/2.0.0-alpha7/slf4j-api-2.0.0-alpha7.jar!/META-INF/versions/9/{color} ---- 差异大概发生在 `jdk.internal.loader.BuiltinClassLoader#findMiscResource` , 我的疑问是是什么造成这种差异? , slf4j 的 `META-INF/versions/*` 的文件为什么会在这里返回? The difference probably occurs in `jdk.internal.loader.BuiltinClassLoader#findMiscResource`, my question is: - What makes this difference? - why does slf4j's' meta-inf / versions / * 'file return here? ============================== Issue deleted ------------------------------ Ceki Gülcü has deleted this issue on 26/May/22 8:05 PM ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-549: Update EventRecodingLogger name to EventRecordingLogger
by QOS.CH (JIRA) 05 May '22

05 May '22

SLF4J / SLF4J-549 [Resolved] Update EventRecodingLogger name to EventRecordingLogger ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-549 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 05/May/22 7:43 PM 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-549: Update EventRecodingLogger name to EventRecordingLogger
by QOS.CH (JIRA) 05 May '22

05 May '22

SLF4J / SLF4J-549 [Open] Update EventRecodingLogger name to EventRecordingLogger ============================== 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-549 ============================== Issue created ------------------------------ Spencer THomas created this issue on 05/May/22 7:13 PM Summary: Update EventRecodingLogger name to EventRecordingLogger Issue Type: Bug Assignee: SLF4J developers list Created: 05/May/22 7:13 PM Priority: Major Reporter: Spencer THomas ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-548: Loading services (plugins) with the caller's ClassLoader
by QOS.CH (JIRA) 01 May '22

01 May '22

SLF4J / SLF4J-548 [Open] Loading services (plugins) with the caller's ClassLoader ============================== 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-548 ============================== 1 comment ------------------------------ pierre on 01/May/22 10:32 PM Hi Ceky, I have read the article [Taxonomy of class loader issues encountered when using Jakarta Commons Logging|https://articles.qos.ch/classloader.html], it seems the problem with JCL's ClassLoader stems from the fact that it uses a Child-first ClassLoader delegation model. I don't want to use a Child-first ClassLoader, I'd like to use the standard Java SDK Parent-first delegation model, but without breaking the extension of the CLASSPATH through ClassLoader inheritance. I don't know enough about Java and ClassLoader, but it seems to me that using the caller's ClassLoader or changing the current.Thread ClassLoader is the same thing. In any case currently it is not possible to load an application using Slf4j and a Service Provider other than using the JRE bootstrap's ClassLoader. (ie: java -cp myapp.jar) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0