[
https://issues.apache.org/jira/browse/SLING-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820743#comment-17820743
]
Julian Reschke edited comment on SLING-12250 at 2/26/24 3:21 PM:
-----------------------------------------------------------------
Well, it should resolve to what is persisted in the repo. If the test *changes*
the repo and the resolves it, it might make time until bg init has finished and
events are processed.
You may want to inspect DEBUG logs...
was (Author: reschke):
Well, it should resolve.
If you have a repro test case, I can have a look.
> Adding Resource with sling:vanityPath set causes mismatch when resolving
> vanity URL (timing issue)
> --------------------------------------------------------------------------------------------------
>
> Key: SLING-12250
> URL: https://issues.apache.org/jira/browse/SLING-12250
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing Sling Mock 3.4.18
> Reporter: Henry Kuijpers
> Priority: Major
>
> It could happen that a Resource containing sling:vanityPath is added and then
> resolved, but the Resource did not end up yet in the vanity logic.
> Observed with JCR_OAK mock context.
> Adding Thread.sleep(1000) fixes the issue, but it's of course not a very good
> solution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
