Health API: Provide means to resolve conflicting result `Fix`es
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the Health API and the Fix/result model introduced by pull request #149. Trace how fixes expose their affected paths and how consumers currently apply them sequentially, then investigate the API design needed for conflicting fixes. Done should provide a decided, documented means to identify or resolve fixes affecting the same resources.
Written by the indexing model from the issue text.
Description
With the merge of https://github.com/cryptomator/cryptofs/pull/149, a result returns an Fix object, which represents the fix for the result (meaning that after applying the fix, the result does not appear again in a subsequent check).
Still, a key problem is not fixed: How to resolve conflicting (aka affecting the same resource) fixes?
It is explicitly spoken of fixes not only results, because a fix can affect more paths than just the result-causing ones. Example
Result A reports a file at the wrong place
/Foo/Bar.c9r. The Fix is to move it to/Baz/Bar.c9r.
The result-causing paths are only/Foo/Bar.c9r, but the fix-affected paths are/Foo/Bar.c9rand/Baz/Bar.c9r.
Every fix alters the state of the filesystem, hence, subsequent fixes (including the same fix) might fail. Currently, the health API does not account for that and only reports all problems of the current filesystem state. The consumer can only execute one fix after another and rerun the health check(s) to fix previously failed fixes.
- Dominant language
- Java
- Stars
- 110
- Forks
- 39
- Avg merge
- 1d 28m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cryptomator/cryptofs
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cryptomator/cryptofs#372 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
cryptomator/cryptofs#246 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
cryptomator/cryptofs#177 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
cryptomator/cryptofs#171 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
cryptomator/cryptofs#153 ·
All issues in cryptomator/cryptofs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
wultra/powerauth-tests#980 ·
-
account bug communication lecture
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
line/centraldogma#1397 ·
Maintainers usually reply within 2 days
-
[Bug]: Fixed/recurring deposit accounts are treated as savings in ownership and listingsPossibly taken @Aana123 claimed this today. Openbug Triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/fineract-consumer-facing#252 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
cryptomator/hub#515 ·