Skip to content
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

Extension activation error: "No such file or directory, open ..." #2204

Closed
bwateratmsft opened this issue Jul 28, 2020 · 2 comments · Fixed by #2205
Closed

Extension activation error: "No such file or directory, open ..." #2204

bwateratmsft opened this issue Jul 28, 2020 · 2 comments · Fixed by #2205
Labels
Milestone

Comments

@bwateratmsft
Copy link
Collaborator

I'm seeing some activation failures, ~.1% failure rate. The overwhelming majority of these failures happen on Windows but there are results for both Linux and Mac.

Error: ENOENT: no such file or directory, open '<REDACTED: user-file-path>'
Stack: Object.openSync fs.js:447:3\nObject.func asar.js:140:31\nObject.func [as openSync] asar.js:140:31

@bwateratmsft bwateratmsft added this to the 1.5.0 milestone Jul 28, 2020
@bwateratmsft bwateratmsft self-assigned this Jul 28, 2020
@bwateratmsft
Copy link
Collaborator Author

This looks similar to some older VSCode issues, e.g. microsoft/vscode#78384.

@bwateratmsft
Copy link
Collaborator Author

I have a theory. The error is not really new, but it used to happen during context init, now happens during activation. The constructor for Dockerode also used to be in context init but is now in activation.

If DOCKER_CERT_PATH is set, docker-modem tries to open ca.pem, cert.pem, and key.pem. This will fail with the error message we see. Additionally, nearly all instances of this error have a host source of env, strengthening this theory.

What I'm not sure about is why almost all of the errors happen on Windows. 🤷

This was referenced Aug 6, 2020
@bwateratmsft bwateratmsft removed their assignment Aug 25, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Sep 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant