- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1651) better error handling in case of missing <if> element in <if><then> pair
by QOS.CH (JIRA) 08 Aug '22

08 Aug '22

1 0

[JIRA] (LOGBACK-1650) Better error checking in case the config file tries to set the level of the ROOT logger to NULL
by QOS.CH (JIRA) 07 Aug '22

07 Aug '22

1 0

[JIRA] Updates for LOGBACK-1650: Better error checking in case the config file tries to set the level of the ROOT logger to NULL
by QOS.CH (JIRA) 07 Aug '22

07 Aug '22

logback / LOGBACK-1650 [Open] Better error checking in case the config file tries to set the level of the ROOT logger to NULL ============================== 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-1650 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 07/Aug/22 11:44 PM Summary: Better error checking in case the config file tries to set the level of the ROOT logger to NULL Issue Type: Bug Affects Versions: 1.3.0-alpha16 Assignee: Logback dev list Components: Joran Created: 07/Aug/22 11:44 PM Fix Versions: 1.3.0-beta0 Priority: Major Reporter: Ceki Gülcü Description: The level of the root logger cannot be set to NULL or INHERITED. In case the user tries to do so, Joran should provide better error handling. Possible config files: {code} <root level="NULL"/> <root> <level value="NULL"/> </root> <logger name="ROOT" level="NULL"/> <logger name="ROOT"> <level value="NULL"/> </logger> {code} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1649: GEventEvaluator not found
by QOS.CH (JIRA) 27 Jul '22

27 Jul '22

logback / LOGBACK-1649 [Open] GEventEvaluator not found ============================== 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-1649 ============================== Issue created ------------------------------ Amira Mannai created this issue on 27/Jul/22 10:43 AM Summary: GEventEvaluator not found Issue Type: Story Affects Versions: 1.2.11 Assignee: Logback dev list Components: logback-classic Created: 27/Jul/22 10:43 AM Environment: After migrating to spring-boot 2.7.2 The logback-classic 1.2.11 is downloaded Labels: logging Priority: Minor Reporter: Amira Mannai Description: The project can no longer be deployed. After analysis I don't find the ch.qos.logback.classic.boolex.GEventEvaluator class under the embedded logback-classic 1.2.11 jar. Here's the console output proving it: {code:java} java.lang.IllegalStateException: Logback configuration error detected: ERROR in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Could not create component [evaluator] of type [ch.qos.logback.classic.boolex.GEventEvaluator] java.lang.ClassNotFoundException: ch.qos.logback.classic.boolex.GEventEvaluator {code} So Why this implementation was deleted? I didn't find a replacement for it in your documentation. Any help will be appreciated. It's not a bug. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1648) Add GitHub token permissions for GitHub Actions workflow
by QOS.CH (JIRA) 21 Jul '22

21 Jul '22

1 0

[JIRA] (LOGBACK-1648) Add GitHub token permissions for GitHub Actions workflow
by QOS.CH (JIRA) 21 Jul '22

21 Jul '22

1 0

[JIRA] Updates for LOGBACK-1648: Add GitHub token permissions for GitHub Actions workflow
by QOS.CH (JIRA) 19 Jul '22

19 Jul '22

logback / LOGBACK-1648 [Open] Add GitHub token permissions for GitHub Actions workflow ============================== 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-1648 ============================== Issue created ------------------------------ Varun Sharma created this issue on 19/Jul/22 7:16 PM Summary: Add GitHub token permissions for GitHub Actions workflow Issue Type: Improvement Assignee: Logback dev list Created: 19/Jul/22 7:16 PM Environment: https://github.com/qos-ch/logback/blob/master/.github/workflows/main.yml Priority: Major Reporter: Varun Sharma Description: This work has been done as part of PR: https://github.com/qos-ch/logback/pull/579 GitHub recommends defining minimum GITHUB_TOKEN permissions for securing GitHub Actions workflows * [https://github.blog/changelog/2021-04-20-github-actions-control-permissions…] * [https://docs.github.com/en/actions/security-guides/automatic-token-authenti…] * The Open Source Security Foundation (OpenSSF) [Scorecards|https://github.com/ossf/scorecard] treats not setting token permissions as a high-risk issue ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1643) gpg key without user id; can't verify logback-classic-1.2.11.pom
by QOS.CH (JIRA) 18 Jul '22

18 Jul '22

1 0

[JIRA] Updates for LOGBACK-1647: logback doesn't create log file with ESAPI2.3.0.0 and ECLIPSE 2021-06
by QOS.CH (JIRA) 11 Jul '22

11 Jul '22

logback / LOGBACK-1647 [Open] logback doesn't create log file with ESAPI2.3.0.0 and ECLIPSE 2021-06 ============================== 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-1647 ============================== Issue created ------------------------------ Vamsi created this issue on 11/Jul/22 5:12 PM Summary: logback doesn't create log file with ESAPI2.3.0.0 and ECLIPSE 2021-06 Issue Type: Bug Affects Versions: 1.2.11 Assignee: Logback dev list Attachments: ESAPI.properties, logback.xml, validation.properties Components: logback-core Created: 11/Jul/22 5:12 PM Environment: * Windows * JDK-11.0.15 * LOGBACK: 1.2.11 * ESAPI: 2.3.0.0 Labels: rollingFileappender Priority: Major Reporter: Vamsi Description: It is an existing project, we were using log4j for logging before. We are recently working on moving to ESAPI. The issue is : We have logs written to file system. When working with IntelliJ, I'm able to successfully implement ESAPI and the logs are successfully getting generated. But when I use the same setup with eclipse 2021-06, it is printing the logs to console but the log file is not getting updated. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1646: Can we have a version of MDC that is case insensitive
by QOS.CH (JIRA) 05 Jul '22

05 Jul '22

logback / LOGBACK-1646 [Open] Can we have a version of MDC that is case insensitive ============================== 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-1646 ============================== Issue created ------------------------------ Michael Bell created this issue on 05/Jul/22 5:53 PM Summary: Can we have a version of MDC that is case insensitive Issue Type: Improvement Assignee: Logback dev list Created: 05/Jul/22 5:53 PM Priority: Major Reporter: Michael Bell Description: One of the major use cases of MDC involves copying context, which includes copy HTTP Headers. HTTP headers are case insensitive. This is exacerabated in recent years by most HTTP/2+ proxies lower casing the headers. Point is copying to a "Dictionary" like MDC and copying back is not by itself problematic, but it's very easy to introduce case sensitive comparisons or contains. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0