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

(Insiders): Error: Error: ENOENT: no such file or directory, stat '/Users/foo/project/.vscode' #71935

Closed
DanTup opened this issue Apr 8, 2019 · 9 comments
Assignees
Labels
file-explorer Explorer widget issues *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach
Milestone

Comments

@DanTup
Copy link
Contributor

DanTup commented Apr 8, 2019

While testing the fix for #71588 I see this in the console when opening a project:

Screenshot 2019-04-08 at 9 41 37 am

@isidorn isidorn self-assigned this Apr 8, 2019
@isidorn isidorn added file-explorer Explorer widget issues under-discussion Issue is under discussion for relevance, priority, approach labels Apr 8, 2019
@isidorn isidorn added this to the Backlog milestone Apr 8, 2019
@DanTup
Copy link
Contributor Author

DanTup commented Apr 16, 2019

I saw this again yesterday, but strangely it has the same path as above - which is an old dev extension I used when testing another issue. That extension was only ever installed into the dev extension host by launching it with F5 from the standard VS Code instance - so it seems like something my have hung around from an old install of a dev extension (it does not show in the extensions list).

@isidorn
Copy link
Contributor

isidorn commented Apr 16, 2019

fyi @sandy081

@sandy081
Copy link
Member

Is it shown only when you are debugging an extension using VS Code or always?

@DanTup
Copy link
Contributor Author

DanTup commented Apr 25, 2019

I think it was only when I was debugging my extension. However, I can't repro now - while trying to fix something the other day, I cleared a lot of the localStorage(?) keys in my Insiders install, and some of them had the path above in. I don't know if that's related - maybe there was a key that referenced that vscode folder at some point and I deleted it? I should've tried to get a call stack from the error above :(

@sandy081
Copy link
Member

If you think extension is running, then my guess would be that our running extension manifests cache might have this entry. But it is just a guess and cannot confirm it. Please try to get more info if you see this again. One thing you can check is to Open Running Extensions editor and see if it has this extension or not.

@DanTup
Copy link
Contributor Author

DanTup commented Apr 25, 2019

If I see it again, I'll do some more digging. It's not often I create new extensions and run them, usually just for repros of issues here, so it might be a while. Feel free to close this in the meantime if you don't think there's anything you can progress.

@kixiro
Copy link

kixiro commented Jun 19, 2019

+1
Version: 1.35.1
Commit: c7d83e5
Date: 2019-06-12T14:27:31.086Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-51-generic

workbench.main.js:1406 ERR Error: Error: ENOENT: no such file or directory, stat '/home/adzyk/.gvm/pkgsets/go1.12.3/global/src//.vscode'

where - is directory opened project

@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Oct 8, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 8, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Oct 8, 2019
@sarbjitsg
Copy link

Same problem. Brand new VS Code, added all extensions required to work with IoT DevKits and:

ENOENT: no such file or directory, mkdir 'C:\Users\User\Documents\iotwbprojects\examples'

Source: Azure IoT Device Workbench (Extension).

Was this fixed? The folder/ files are not open any where else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
file-explorer Explorer widget issues *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

5 participants