-
Notifications
You must be signed in to change notification settings - Fork 345
DAOS-18933 ci: fix PermissionError in pre-commit clang-format hook #18183
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
Open
knard38
wants to merge
3
commits into
master
Choose a base branch
from
ckochhof/fix/master/daos-18933/patch-001
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+4
−3
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why you decided to use both? Why not just replace the unreliable one with a reliable one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SCons.Scriptships a no-op stub forWhereIsthat is active whenever the module is imported outside a full SCons build (i.e. the pre-commit hook context).On my machine:
Replacing
WhereIsentirely would fix the crash but lose the SCons-environment-aware lookup during actual builds. TheorkeepsWhereIswhen it works and falls back toshutil.whichwhen the stub is in effect.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a little messy. 😅
Another thought. Why not use
shutil.which('clang-format')in theWhereIsstub?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did not wanted to touch to the fake_scons stubs as I am not sure of their purpose.
I am going to investigate as I agree that it should be a better solution: I have to check that I am not breaking anything (test, etc.).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After investigating, I'd keep the fix in
extra.pyrather than changing the stub.fake_sconsis a pylint shim, as indicated by its docstring "Fake scons environment shutting up pylint on SCons files" — its sole purpose is to provide importableSCons.*stubs so that pylint can analyse SCons-based Python files without crashing onImportError. Its functions deliberately do nothing — that is the intended contract.The root cause of the crash is that
utils/sl/fake_sconsends up onPYTHONPATHfor any developer who sources the standard DAOS dev environment (it is needed fordaos_pylint.py). As a result, any standalone Python invocation — including the pre-commit hook — resolvesSCons.Scriptto the shim instead of the real SCons, and gets the no-opWhereIsstub.If I am correct, making the stub functional with
shutil.whichwould silently change its behaviour for pylint runs and could mask similar issues in the future. The fix inextra.pyis the right level: it defends the one real caller against whateverWhereIsreturns, regardless of whichSCons.Scriptis on the path.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it is no longer true since it is being used outside of this context. You have to consider all the scripts as they are being used. Fixing weakness of the shim in the code is a bad approach.
We either will find a way to load a different shim so you will again have:
OR the shim we use stops being pylint-only and we have to make it actually usable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with you that the proposed solution is not ideal from an architectural standpoint.
From my understanding, the shim ends up in the pre-commit context not by design, but accidentally —
utils/sl/fake_sconsis added toPYTHONPATHby the standard DAOS dev environment (needed fordaos_pylint.py), so any standalone Python invocation, including the pre-commit hook, picks it up. I do not think it was intended to be used there.At this point, the shim still has no real functionality (mostly no-ops), with just a few exceptions needed by pylint.
As I see it, each solution has its own trade-offs:
extra.py(current PR):WhereIs(and similar) properly in the existing shim.I do not have enough context on the build system to judge which approach fits best here.
@jolivier23 and @daltonbohning do you have any opinion on whether to change the shim or keep the fix in
extra.py?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is setting this? Personally, I've never run into this issue with the stub so I'm not sure what exactly the issue is