-
Notifications
You must be signed in to change notification settings - Fork 198
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
Ensure directory has user "execute" permissions so it is accessible #1982
Conversation
40c1057
to
5f807b7
Compare
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSIContainer
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference (preview)
|
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.
LGTM. Thanks for the extra care in well-written code and tests!
Fixes #1691
I spotted this behavior on a mac after an upgrade in the course of doing other work. The fix for now is to ensure that the directory has the "x" bit set for the user so that it's accessible to the user. At this point I'm not entirely sure why an outside process is resetting this bit during OS upgrades. It would seem that the upgrade is determining that this directory should not be accessible.
There is a
repairHomePermissions
tool on macOS which can be run in recovery mode. Running that tool does not change these file permissions. We'd need to test an OS upgrade directly in detail to learn more.