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

Health API: Provide means to resolve conflicting result Fixes #151

Open
infeo opened this issue Nov 22, 2022 · 0 comments
Open

Health API: Provide means to resolve conflicting result Fixes #151

infeo opened this issue Nov 22, 2022 · 0 comments

Comments

@infeo
Copy link
Member

infeo commented Nov 22, 2022

With the merge of #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.c9r and /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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant