April 2024 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1766) JaninoEventEvaluator Doesn't support Marker
by logback developers list 08 Apr '24

08 Apr '24

1 0

[JIRA] (LOGBACK-1759) LoggerContext.reset() closes Jansi-OutputStream
by logback developers list 07 Apr '24

07 Apr '24

1 0

[JIRA] (LOGBACK-1393) The ch.qos.logback.core.rolling.helper.FileFilterUtil.afterLastSlash function may cause NPE problem
by logback developers list 07 Apr '24

07 Apr '24

1 0

[JIRA] (LOGBACK-1393) The ch.qos.logback.core.rolling.helper.FileFilterUtil.afterLastSlash function may cause NPE problem
by logback developers list 07 Apr '24

07 Apr '24

1 0

[JIRA] (LOGBACK-1767) In RollingAppender, setting a triggering policy a second time will cause errors
by logback developers list 05 Apr '24

05 Apr '24

1 0

[JIRA] Updates for LOGBACK-1767: In RollingAppender, setting a triggering policy a second time will cause errors
by logback developers list 05 Apr '24

05 Apr '24

logback / LOGBACK-1767 [Open] In RollingAppender, setting a triggering policy a second time will cause errors ============================== 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/LOGBACK-1767 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 05/Apr/24 21:50 Summary: In RollingAppender, setting a triggering policy a second time will cause errors Issue Type: Bug Assignee: Logback dev list Created: 05/Apr/24 21:50 Priority: Major Reporter: Ceki Gülcü Description: A checks warning users that setting a triggering policy a second time will cause errors ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] (LOGBACK-1759) LoggerContext.reset() closes Jansi-OutputStream
by logback developers list 05 Apr '24

05 Apr '24

1 0

[JIRA] Updates for LOGBACK-1766: JaninoEventEvaluator Doesn't support Marker
by logback developers list 05 Apr '24

05 Apr '24

logback / LOGBACK-1766 [Open] JaninoEventEvaluator Doesn't support Marker ============================== 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/LOGBACK-1766 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 05/Apr/24 6:45 Summary: JaninoEventEvaluator Doesn't support Marker Issue Type: Bug Assignee: Logback dev list Created: 05/Apr/24 6:45 Environment: I want to filter my log per the expression marker != null && (marker.contains("SYSTEM_OUT") || level==ERROR). But recently I upgraded the logback to the latest version and found it doesn't work. I checked the document and it says it still supports marker, see https://logback.qos.ch/manual/appenders.html#marker_JaninoEventEvaluator. But from the source code I see it has already comment out https://github.com/qos-ch/logback/blob/master/logback-classic/src/main/java…. I also tried to workaround this by adding two appenders and one for log level filter and another for OnMarkerEvaluator, but the performance decreased significantly and it would be obvious if I have a large set of data that need to be logged. Any thoughts on this? Fix Versions: 1.5.0 Priority: Major Reporter: Ceki Gülcü ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)

1 0

[JIRA] (LOGBACK-1759) LoggerContext.reset() closes Jansi-OutputStream
by logback developers list 04 Apr '24

04 Apr '24

1 0

[JIRA] (LOGBACK-1707) KeyValue pair does not work in Fluent API
by logback developers list 04 Apr '24

04 Apr '24

1 0