Repository navigation
'clasp list' Shows ' EPERM: operation not permitted' Error When Installed as None Admin User #409
Description
Expected Behavior
clasp list should list projects
Actual Behavior
Showing error message
Error retrieving access token: Error: EPERM: operation not permitted, open '%USERPROFILE%.clasprc.json'
Fixed by change the permission of '.clasprc.json' file from 'read only' to 'read-write'
Steps to Reproduce the Problem
- Install nodejs (with npm) from the zipped package to %USERPROFILE% folder (as Windows local user, not admin)
- npm install clasp (and verify)
- run
clasp list - Error message shown
- Examine the permission of .clasprc.json file, it should be 'read only'
- Uncheck the 'read only' option
- run
clasp listagain. Issue should be gone
Specifications
- Node version (
node -v): v11.2.0 - Version (
clasp -v): 1.6.3 - OS (Mac/Linux/Windows): Windows 10 v1803
Activity
grant commentedon Nov 20, 2018
OK. I'm not sure why
.clasprc.jsonwhen writing the file. Maybe an issue here: https://github.com/grant/dotf/blob/master/index.js#L37PRs welcome to
dotf.It seems like a Windows issue too.
prprhyt commentedon Nov 21, 2018
I think too.
chmod/chmodSync occurred to unexpected behavior in Windows.
So, I suggest that we should modify dotf to prevent executing chmodSync when dotf is running on Windows.
See:
nodejs/node-v0.x-archive#4812
grant commentedon Nov 21, 2018
That looks like a very old issue in Node.
prprhyt commentedon Nov 21, 2018
Oops. I'm sorry.
I found description about mode of fs.chmod() on Windows.
@grant
Do you think it is related to this issue?
https://github.com/nodejs/node/blob/master/doc/api/fs.md#fschmodpath-mode-callback
grant commentedon Nov 24, 2018
@prprhyt @bv-vd Looks related to Windows/the linked issue.
Can you make a PR to not
chmod/chmodSyncon Windows fordotf?prprhyt commentedon Nov 24, 2018
@grant
OK. I'll give it a try!
grant commentedon Nov 25, 2018
@prprhyt I added
dotf@1.2that includes the patch you wrote.Can you try updating
claspwith this version and see if the Windows issue is fixed?grant commentedon Nov 26, 2018
@bv-vd The fix should be applied in the
masterbranch of this repo. If you see it still occurring there, please reopen this issue.@prprhyt Created PRs to fix this issue.
imthenachoman commentedon Dec 10, 2019
I don't know if I should open a new issue but I was getting a similar error when I had hidden the
.clasprc.jsonfile through Windows.I had to un-hide the file for it to work. Not sure why
clasprun from PowerShell would need the file to be un-hidden?PopGoesTheWza commentedon Dec 10, 2019
@imthenachoman Looks like a NodeJS limitation: nodejs/node#14553
Not sure yet how to implement a fix
imthenachoman commentedon Dec 10, 2019
@PopGoesTheWza Yeah. Very strange issue. I don't fully understand the technical reason but I assume it has something to do with how Microsoft did something. Oh well. Not a big deal.
PopGoesTheWza commentedon Dec 10, 2019
I'd adventure a wild guess: Linux and Mac OS have similar POSIX compliant file systems which do not have an
hiddenattribute. Such attribute I only encounter on Microsoft OSes (DOS and Windows) and a few long since forgotten systems. In order to fully support Windows differences, one would need to either introduce in the NodeJS code base too much specific code, or leave up to apps and package developer to handle it.https://en.wikipedia.org/wiki/Hidden_file_and_hidden_directory