[
https://issues.apache.org/jira/browse/YUNIKORN-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikandan R resolved YUNIKORN-3312.
------------------------------------
Fix Version/s: 1.9.0
Resolution: Fixed
> fix logger setup in core
> ------------------------
>
> Key: YUNIKORN-3312
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3312
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - common
> Affects Versions: 1.9.0
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.9.0
>
>
> The scoped logging setup uses a list and variable declaration that must be in
> sync.
> The current list in the core is not in sync and this could lead to a panic.
> The panic currently does not occur in due to a reused ID for the last logger.
> The last two loggers are now the same.
> Fixing that issue causes a panic if the log level for the last logger in the
> list is accessed as we try to read outside of the fixed size slice.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
