You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/06/10 09:13:00 UTC
[jira] [Closed] (SLING-10202) Incorrect evaluation of executed
hashes
[ https://issues.apache.org/jira/browse/SLING-10202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus closed SLING-10202.
-----------------------------------
> Incorrect evaluation of executed hashes
> ---------------------------------------
>
> Key: SLING-10202
> URL: https://issues.apache.org/jira/browse/SLING-10202
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: JCR Package Init 1.0.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: JCR Package Init 1.0.4
>
>
> Only the first executed hash is compared against the list of candidates in https://github.com/apache/sling-org-apache-sling-jcr-packageinit/blob/4a78330354e4d65402ec8bf37dfda20346826651/src/main/java/org/apache/sling/jcr/packageinit/impl/ExecutionPlanRepoInitializer.java#L127.
> If another item in the executed hash list is containing the hash already, the execution plan is still scheduled for execution. I think a nested loop is somehow missing here.
> The assumption that the execution plan order in candidates and processed hashes is always the same is wrong.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)