Skip to content

Conversation

@cstamas
Copy link
Member

@cstamas cstamas commented Dec 10, 2025

Within ArtifactResolver there was a subtle bug, caused by unintentional lazy evaluation of logical OR. In case filter is present, it is ONLY and only LRM availability that drives the logic.

Within ArtifactResolver there was a subtle bug, caused by
unintentional lazy evaluation of logical OR. In case filter is
present, it is ONLY and only lrm availability that drives
the logic.
@cstamas cstamas self-assigned this Dec 10, 2025
@cstamas cstamas added the bug Something isn't working label Dec 10, 2025
@cstamas cstamas added this to the 2.0.14 milestone Dec 10, 2025
@cstamas cstamas requested a review from gnodet December 10, 2025 21:02
@cstamas cstamas changed the title Bug: GH-1703 Two Bug: GH-1703 Locally cached artifacts defy RRF Dec 10, 2025
@cstamas
Copy link
Member Author

cstamas commented Dec 10, 2025

This applies to Resolver 1.9 as well:

boolean found = (filter != null && local.isAvailable()) || isLocallyInstalled(local, versionResult);

@cstamas cstamas marked this pull request as ready for review December 10, 2025 21:31
@cstamas cstamas merged commit f815732 into apache:master Dec 11, 2025
27 of 28 checks passed
@cstamas cstamas deleted the gh-1703-two branch December 11, 2025 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GroupId filtering doesn't allow group children as documented

2 participants