-
-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
EACCESS: permission denied on ignored directory #737
Comments
I took a look at the code, and the error seems to come from the call to EDIT: tracked down to the call to EDIT 2: got too deep, now I’m down to Here’s my walkthrough:
I think this is a bug, but somehow, if I change the code of
But that doesn’t resolve the issue… It’s getting late and I’m tired rn, I’ll try to continue tomorrow. |
Looking back at this, I now think I understand what does the I think this is the issue, because it’s actually trying to search for an ignore file inside the If I update the code of Something like that (dirty): export const isIgnoredByIgnoreFiles = async (patterns, options) => {
const {cwd, suppressErrors, deep} = normalizeOptions(options);
const paths = await fastGlob(patterns, {
cwd,
suppressErrors,
deep,
...ignoreFilesGlobOptions,
ignore: [...ignoreFilesGlobOptions.ignore, ...options.ignore],
});
const files = await Promise.all(
paths.map(async filePath => ({
filePath,
content: await fs.promises.readFile(filePath, 'utf8'),
})),
);
return getIsIgnoredPredicate(files, cwd);
};
|
That issue and PR seem to be closed 🎉 |
I have the following issue trying to run xo on my project :
I created a repository to reproduce this issue.
To better explain, I have a MySQL container running alongside my Node.js API, and I’m mounting its data directory in a
.data
directory at my project root. I added the.data
to.gitignore
, expecting xo to actually ignore it, but it still tries to scan the subdirectories of.data
, as per the error message.Also tried adding
.data/**/*
to.gitignore
, as well as adding them to theignores
xo config field, with same results.EDIT: I know I can fix this by running something like this:
sudo chgrp -R $(whoami) .data/mysql
but I still think this is a bug.The text was updated successfully, but these errors were encountered: