October 2021 - slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-524: Please add the SLF4J Release information to the 1st message print to the console
by QOS.CH (JIRA) 26 Oct '21

26 Oct '21

SLF4J / SLF4J-524 [Open] Please add the SLF4J Release information to the 1st message print to the console ============================== 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-524 ============================== 1 comment ------------------------------ Ceki Gülcü on 26/Oct/21 9:06 PM Possible implementation via: {code:java} this.getClass().getPackage().getImplementationVersion(); {code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-524: Please add the SLF4J Release information to the 1st message print to the console
by QOS.CH (JIRA) 26 Oct '21

26 Oct '21

SLF4J / SLF4J-524 [Open] Please add the SLF4J Release information to the 1st message print to the console ============================== 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-524 ============================== Issue created ------------------------------ Jehoschua created this issue on 26/Oct/21 8:19 PM Summary: Please add the SLF4J Release information to the 1st message print to the console Issue Type: Improvement Affects Versions: 2.0.0-alpha4 Assignee: SLF4J developers list Components: Core API Created: 26/Oct/21 8:19 PM Environment: Not relevant Labels: suggestion Priority: Minor Reporter: Jehoschua Description: Hello thanks a lot for sharing your great work! When we work with different projects, it is often a mystery which SLF4J version is active if we get this kind of message: {{SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".}} {{SLF4J: Defaulting to no-operation (NOP) logger implementation}} {{SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.}} Could you please write the SLF4J release information in the first message that is printed to the console? I guess that this additional information does not bother, but can be a good help over and over again. Thanks a lot, kind regards, Thomas ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-471: CharSequence and varargs
by QOS.CH (JIRA) 21 Oct '21

21 Oct '21

SLF4J / SLF4J-471 [Open] CharSequence and varargs ============================== 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-471 ============================== 1 comment ------------------------------ Endre Stølsvik on 21/Oct/21 11:47 PM One basic reason for why CharSequence is better, is that a StringBuilder is a CharSequence. Right now, I am constructing a message with lots of ifs-and-buts, and then when I want to log it, i _have to_ do .toString() on it, creating a new object with a new char-array. But the other is what OP mentions: You might want to pre-allocate log char arrays for a thread, and then reuse them - avoiding object creations. This would actually work nicely with StringBuilders, using setLength(0) to "clear" them. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-523: IllegalArgumentException with tag name having 23 characters
by QOS.CH (JIRA) 07 Oct '21

07 Oct '21

SLF4J / SLF4J-523 [Open] IllegalArgumentException with tag name having 23 characters ============================== 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-523 ============================== Issue created ------------------------------ Yongsik Moon created this issue on 07/Oct/21 6:57 AM Summary: IllegalArgumentException with tag name having 23 characters Issue Type: Bug Affects Versions: 1.7.30 Assignee: SLF4J developers list Attachments: image-2021-10-07-15-56-27-225.png Components: slf4j-android Created: 07/Oct/21 6:57 AM Environment: * Software platform : Android 4.4 and 7 * slf4j-api:1.7.10 * slf4j-android: 1.7.30 or higher * tag name : "ChannelServerSocket_١٠٠" (in Arabic, the length is 23) Priority: Major Reporter: Yongsik Moon Severity: major Description: With the tag name "ChannelServerSocket_١٠٠", IllegalArgumentException is thrown. I think JNI uses UTF-8 string to count length. !image-2021-10-07-15-56-27-225.png|width=604,height=219! ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0