-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Since 1.2.1: error Could not open cafile: EISDIR: illegal operation on a directory, read #4695
Comments
Closing as a duplicate #4336 |
Oops, my fault... I saw 2 bugs with
I did a |
This is because you're using yarn < 1.2.1 you need 1.2.1 otherwise you get into #4687 which is fixed in 1.2.1 only. Actually I deleted my previous comment about the duplicate since I saw in the latter comments in the thread that the while the original issue was a configuration error with 1.0.1. The issue remained without this config error in 1.2.0. So it still may be a duplicate, this issue however adds a repro-script so we could drop the need-repro from the tag. |
Ah, good catch. I have multiple yarn builds running around in different directories and ran the primary Yarn command with 1.2.1, but 1.0.2 is in my path still, so the script commands ended up calling 1.0.2. If I put 1.2.1 in my path, I see the errors:
|
I added a line to print the "cafile" that it is trying to load:
Somehow through this chain of build scripts, Yarn is getting |
Do you see something in the recent changes from 1.0.2 to 1.2.1 that would cause that ? How is yarn usually getting a cafile ? |
Seems to be caused by #4605 Specifically the line: 3178e07#diff-9d9a6cd82f41984872a66a3ab0d440c4R199 Previously an unset cafile would return empty string , now it returns the project home dir.
but the setting is no longer empty string. It tries to load the home directory as a cert file and throws an Edit Also noticing that if you run
This being empty string instead of undefined exposes the flaw in the logic above that changes empty string to the full path. Edit 2 The env var above is not set by Yarn, it is set by NPM. So, this is a result of a command invoking an |
I'm seeing the same error on |
* [#4695] Do not convert empty string to cwd path. * added test file for config.js
Thanks! |
Is there a workaround available in the meantime? eg; a safe value for EDIT: |
Avoids yarn issue yarnpkg/yarn#4695
* [yarnpkg#4695] Do not convert empty string to cwd path. * added test file for config.js
What is the current behavior?
Using yarn with workspaces while building Theia I now get erros like:
If the current behavior is a bug, please provide the steps to reproduce.
You can reproduce with;
What is the expected behavior?
With yarn 1.0.2 I do not get this error.
Please mention your node.js, yarn and operating system version.
npm --version
5.3.0
OS: linux
Note you can also use this Dockerfile to reproduce:
You will see the error while doing a
docker build -t theia .
The text was updated successfully, but these errors were encountered: