Skip to content

Actions: apache/logging-log4j2

Actions

Check labels

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
labeler.yaml
757 workflow run results
757 workflow run results

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

apparent deadlock in InternalLoggerRegistry.getLogger() Check labels #1511: Issue comment #3252 (comment) created by jpcmonster
14s
14s
Fix ConcurrentModificationException in updateLoggers() Check labels #1510: Issue comment #3235 (comment) created by ppkarwasz
3s
3s
Fix ConcurrentModificationException in updateLoggers() Check labels #1509: Issue comment #3235 (comment) created by garydgregory
3s
3s
ConcurrentModificationException in LoggerContext due to race condition Check labels #1508: Issue comment #3234 (comment) created by kelunik
11s
11s
Fix ConcurrentModificationException in updateLoggers() Check labels #1507: Issue comment #3235 (comment) created by kelunik
3s
3s
Fix Android-related issues in Log4j Core Check labels #1506: Issue comment #3071 (comment) created by ppkarwasz
3s
3s
Fix Android-related issues in Log4j Core Check labels #1505: Issue comment #3071 (comment) created by ahasbini
3s
3s
apparent deadlock in InternalLoggerRegistry.getLogger() Check labels #1504: Issue comment #3252 (comment) created by ppkarwasz
13s
13s
ConcurrectModificationException while adjusting log-level in runtime Check labels #1503: Issue comment #3283 (comment) created by ppkarwasz
10s
10s
When logging exceptions, the exception stack traces include dynamically generated class names, which leads to a memory leak. Check labels #1502: Issue comment #3282 (comment) created by Tonys-L
13s
13s
Add a Jakarta JMS Appender #2295 Check labels #1501: Issue comment #3247 (comment) created by garydgregory
2s
2s
Add a Jakarta JMS Appender #2295 Check labels #1500: Issue comment #3247 (comment) created by garydgregory
2s
2s
When logging exceptions, the exception stack traces include dynamically generated class names, which leads to a memory leak. Check labels #1499: Issue comment #3282 (comment) created by ppkarwasz
18s
18s
When logging exceptions, the exception stack traces include dynamically generated class names, which leads to a memory leak. Check labels #1498: Issue comment #3282 (comment) created by Tonys-L
9s
9s
When logging exceptions, the exception stack traces include dynamically generated class names, which leads to a memory leak. Check labels #1497: Issue comment #3282 (comment) created by Tonys-L
12s
12s
ConcurrectModificationException while adjusting log-level in runtime Check labels #1496: Issue comment #3283 (comment) created by tnleeuw
14s
14s
Fix ConcurrentModificationException in updateLoggers() Check labels #1495: Issue comment #3235 (comment) created by tnleeuw
1s
1s
ConcurrectModificationException while adjusting log-level in runtime Check labels #1494: Issue comment #3283 (comment) created by ppkarwasz
11s
11s
Fix ConcurrentModificationException in updateLoggers() Check labels #1493: Issue comment #3235 (comment) created by ppkarwasz
2s
2s
When logging exceptions, the exception stack traces include dynamically generated class names, which leads to a memory leak. Check labels #1492: Issue comment #3282 (comment) created by garydgregory
11s
11s
When logging exceptions, the exception stack traces include dynamically generated class names, which leads to a memory leak. Check labels #1491: Issue comment #3282 (comment) created by ppkarwasz
12s
12s
ConcurrectModificationException while adjusting log-level in runtime Check labels #1490: Issue comment #3283 (comment) created by tnleeuw
10s
10s
ConcurrectModificationException while adjusting log-level in runtime Check labels #1489: Issue comment #3283 (comment) created by tnleeuw
11s
11s
ConcurrentModificationException in LoggerContext due to race condition Check labels #1488: Issue comment #3234 (comment) created by tnleeuw
15s
15s
ConcurrectModificationException while adjusting log-level in runtime Check labels #1487: Issue comment #3283 (comment) created by vy
10s
10s
ProTip! You can narrow down the results and go further in time using created:<2024-12-06 or the other filters available.