Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CorpseFinder: Fix detection of nested corpses on public storage #1454

Merged
merged 1 commit into from
Nov 6, 2024

Conversation

d4rken
Copy link
Member

@d4rken d4rken commented Nov 6, 2024

The marker segments are prefix-free, so we also need to compare it with the prefix-free area information, otherwise we get no match. e.g.

Before: {/storage/emulated/0/Android}.isAncestorOf(Android/cache) returned false

Now: {Android}.isAncestorOf(Android/cache) returns true

The marker segments are prefix-free, so we also need to compare it with the prefix-free area information, otherwise we get no match.
e.g.
Before: `{/storage/emulated/0/Android}.isAncestorOf(Android/cache)`
Now:  `{Android}.isAncestorOf(Android/cache)`
@d4rken d4rken added bug Something isn't working as expected c: CorpseFinder labels Nov 6, 2024
@d4rken d4rken merged commit c270273 into main Nov 6, 2024
16 checks passed
@d4rken d4rken deleted the corpsefinder-nested-matches branch November 6, 2024 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected c: CorpseFinder
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant