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

[JIRA] Updates for SLF4J-509: Append log records to the end of the log file
by QOS.CH (JIRA) 15 Feb '21

15 Feb '21

SLF4J / SLF4J-509 [Open] Append log records to the end of the log file ============================== 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-509 ============================== Issue created ------------------------------ Dmitriy Fedoriv created this issue on 15/Feb/21 6:11 AM Summary: Append log records to the end of the log file Issue Type: Improvement Assignee: SLF4J developers list Components: slf4j-simple Created: 15/Feb/21 6:11 AM Labels: FileAppender appender Priority: Minor Reporter: Dmitriy Fedoriv Description: It would be great to have the ability to aggregate all log records in a single log file. As a short term solution, we could expose a new option to control FileOutputStream append, as a long term - design simple log retention functionality. `org.slf4j.simpleLogger.logFileAppend` When true, records will be appended to the end of the file. When set to false, the file will be cleared before new records are written. Defaults to `false` for backward compatibility. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-508: Control log level output in the simple logger pattern layout
by QOS.CH (JIRA) 15 Feb '21

15 Feb '21

SLF4J / SLF4J-508 [Open] Control log level output in the simple logger pattern layout ============================== 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-508 ============================== Issue created ------------------------------ Dmitriy Fedoriv created this issue on 15/Feb/21 3:20 AM Summary: Control log level output in the simple logger pattern layout Issue Type: Improvement Assignee: SLF4J developers list Components: slf4j-simple Created: 15/Feb/21 3:20 AM Labels: layouts pattern Priority: Minor Reporter: Dmitriy Fedoriv Description: Dear QoS team, The justification for the improvement is to provide a smooth and backward-compatible switch between Java standard output and Slf4J SimpleLogger without any changes in output message pattern. The vast majority of static code analyzers consider printing directly to standard output as a bad practice, proposing to use a dedicated logger as a solution (e.g. https://rules.sonarsource.com/java/RSPEC-106) In some cases, the output format of a message could be restricted and not subject to change. That leaves the message format pattern as "<message><line_separator>" for the dedicated logger. At more "advanced" logging frameworks this can be controlled by setting different pattern layouts but in the slf4j-simple module, it's handled by simplelogger.properties configuration or system properties. The module already has specific properties to control the output of the date-time, thread name, and logger name, but missing one more to skip log level output such as "org.slf4j.simpleLogger.showLogLevel=true". ============================== 1 comment ------------------------------ Dmitriy Fedoriv on 15/Feb/21 3:26 AM Here is the link to related PR - https://github.com/qos-ch/slf4j/pull/256 ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-507: Logger.getLogger (compact initialization)
by QOS.CH (JIRA) 08 Feb '21

08 Feb '21

SLF4J / SLF4J-507 [Open] Logger.getLogger (compact initialization) ============================== 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-507 ============================== Issue created ------------------------------ Sergey Chernov created this issue on 08/Feb/21 8:02 AM Summary: Logger.getLogger (compact initialization) Issue Type: Improvement Affects Versions: 2.0.0-alpha1 Assignee: SLF4J developers list Components: Core API Created: 08/Feb/21 8:02 AM Environment: Manual definition of {{Logger}} field in class. Priority: Minor Reporter: Sergey Chernov Description: Most common use case of logger declaration looks like {code} import org.slf4j.Logger; import org.slf4j.LoggerFactory; ... private static final Logger logger = LoggerFactory.getLogger(CurrentType.class); {code} It's almost fine, but it could be more compact: {code} import org.slf4j.Logger; ... private static final Logger logger = Logger.getLogger(CurrentType.class); {code} Before java 8 it was not possible ({{Logger}} is an interface, not abstract class), now since the minimum required version is 9, the static initialization method can be introduced in the interface. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-497: SLF4JLocationAwareLog avoid building message when logging level is disabled
by QOS.CH (JIRA) 08 Feb '21

08 Feb '21

SLF4J / SLF4J-497 [Open] SLF4JLocationAwareLog avoid building message when logging level is disabled ============================== 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-497 ============================== 1 comment ------------------------------ Ondrej Zizka on 08/Feb/21 2:13 AM Big YES for this feature. JUL has had it that for several years now. And this is the easiest way to avoid string building. E.g. in Kontlin: log.info \{ "Very big entity whose toString() will take a second if called: ${bigEntity}" } ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

JDK 16 is now in the Release Candidate Phase
by Rory O'Donnell 05 Feb '21

05 Feb '21

*Hi Ceki, * *Per the JDK 16 schedule , we are in the Release Candidate Phase**[1] .* *Please advise if you find any issues while testing the latest Early Access builds.* * Schedule for JDK 16 o *2021/02/04 Initial Release Candidate* o 2021/02/18 Final Release Candidate o 2021/03/16 General Availability * Release Notes [2] OpenJDK 16 Early Access build 35**is now available at http://jdk.java.net/16 <http://jdk.java.net/16> * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Features [3] - the overall feature set is frozen. No further JEPs will be targeted to this release. * Changes in recent builds that maybe of interest: o Build 34: + JDK-8259025: Record compact constructor using Objects.requireNonNull # Reported by JUnit5 o Build 32: + JDK-8259014: Incomplete support for Unix domain sockets in Windows 2019 Server * JDK 16 - topics of interest: o Unix domain socket channels (JEP-380) overview: https://inside.java/2021/02/03/jep380-unix-domain-sockets-channels/ <https://inside.java/2021/02/03/jep380-unix-domain-sockets-channels/> o Java Feature Spotlight: Pattern Matching https://inside.java/2021/01/22/feature-spotlight-pattern-matching/ <https://inside.java/2021/01/22/feature-spotlight-pattern-matching/> o Foreign Memory Access - Pulling all the thread https://inside.java/2021/01/25/memory-access-pulling-all-the-threads/ <https://inside.java/2021/01/25/memory-access-pulling-all-the-threads/> * General – topic of interest: o Inside Java Episode 11 “How to contribute to OpenJDK” with Stuart Marks and Jesper Wilhelmsson https://inside.java/2021/01/29/podcast-011/ <https://inside.java/2021/01/29/podcast-011/> Project Lanai EA 9 Build 17-lanai+2-49 (2021/1/20) <http://jdk.java.net/lanai/> is available now * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html> * EA builds are intended for developers looking to test and provide feedback on using Project Lanai. * This is a macOS-specific project which implements a new Java 2D graphics rendering pipeline for macOS. * Project Lanai Wiki: https://wiki.openjdk.java.net/display/lanai/Main <https://wiki.openjdk.java.net/display/lanai/Main> * Please send feedback via e-mail to lanai-dev(a)openjdk.java.net <mailto:lanai-dev@openjdk.java.net>. To send e-mail to this address you must first subscribe to the mailing list <https://mail.openjdk.java.net/mailman/listinfo/lanai-dev>. Project Loom Build 17-loom+2-42 (2021/1/14) <http://jdk.java.net/loom/> based on JDK-17+5 <https://github.com/openjdk/jdk/releases/tag/jdk-17%2B5> is available now * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html> * These builds are intended for developers looking to "kick the tyres" and provide feedback on using the API or by sending bug reports. * API Javadoc : https://download.java.net/java/early_access/loom/docs/api/ <https://download.java.net/java/early_access/loom/docs/api/> * Please send feedback via e-mail to loom-dev(a)openjdk.java.net <mailto:loom-dev@openjdk.java.net>. To send e-mail to this address you must first subscribe to the mailing list <http://mail.openjdk.java.net/mailman/listinfo/loom-dev>. OpenJDK 17 Early Access build 8**is now available at http://jdk.java.net/17 <http://jdk.java.net/17> * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Changes in recent builds that maybe of interest: o Build 8: + JDK-8222850: Misleading cascade compiler error in switch expression with undefined vars # Reported by jOOQ. + JDK-8217633: Configurable extensions with system properties + JDK-8249867: DOM LSSerializer control of newline after XML header + JDK-8256421: Added 2 HARICA Root CA Certificates + JDK-8259801: Enable XML Signature secure validation mode by default o Build 7: + JDK-8165276: Spec states to invoke the premain method in an agent class if it's public but implementation differs + JDK-8256895: Add support for RFC 8954: Online Certificate Status Protocol (OCSP) Nonce Extension o Build 6: + JDK-8259048: (tz) Upgrade time-zone data to tzdata2020f January 2021 Critical Patch Update Released: * As part of the Jan 2021 CPU we released JDK 15.0.2, JDK 11.0.10 LTS, JDK 8u281, and JDK 7u291 as well as OpenJDK 15.0.2 (publicly available). Rgds, Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2021-February/005062.html <https://mail.openjdk.java.net/pipermail/jdk-dev/2021-February/005062.html> [2] https://jdk.java.net/16/release-notes <https://jdk.java.net/16/release-notes> [3] http://openjdk.java.net/projects/jdk/16/ <http://openjdk.java.net/projects/jdk/16/> -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] Updates for SLF4J-506: org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data.
by QOS.CH (JIRA) 02 Feb '21

02 Feb '21

SLF4J / SLF4J-506 [Open] org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data. ============================== 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-506 ============================== Issue created ------------------------------ Simon Mulser created this issue on 02/Feb/21 9:30 AM Summary: org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data. Issue Type: Bug Affects Versions: 1.7.30 Assignee: SLF4J developers list Components: slf4j-ext Created: 02/Feb/21 9:30 AM Environment: https://nvd.nist.gov/vuln/detail/CVE-2018-8088 Priority: Major Reporter: Simon Mulser External issue URL: https://nvd.nist.gov/vuln/detail/CVE-2018-8088 Severity: major ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0