[SLING-10202] Incorrect evaluation of executed hashes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Package Init 1.0.2
• Fix Version/s: JCR Package Init 1.0.4
• Component/s: Repoinit
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 09/Mar/21 17:23
• Updated: 10/Jun/21 09:12
• Resolved: 16/Mar/21 15:17

Description

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.

Issue Links

• links to: GitHub Pull Request #5