You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2025/03/06 08:20:00 UTC

[jira] [Updated] (SLING-12679) ResourceResolver: incorrect metrics init

     [ https://issues.apache.org/jira/browse/SLING-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated SLING-12679:
-----------------------------------
        Parent: SLING-12695
    Issue Type: Sub-task  (was: Bug)

> ResourceResolver: incorrect metrics init
> ----------------------------------------
>
>                 Key: SLING-12679
>                 URL: https://issues.apache.org/jira/browse/SLING-12679
>             Project: Sling
>          Issue Type: Sub-task
>          Components: ResourceResolver
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: Resource Resolver 1.12.6
>
>
> See
>   https://github.com/apache/sling-org-apache-sling-resourceresolver/blame/08ebd4401fc2b3a3569119ab6cc33e2094e89817/src/main/java/org/apache/sling/resourceresolver/impl/mapping/MapEntries.java#L179
> {code}
> this.metrics.get().setNumberOfResourcesWithAliasesOnStartupSupplier(detectedInvalidAliases::get);
> {code}
> Unfortunately, this does not test coverage, as all checks for actual values bypass the metrics object and go directly to the counters.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)