Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: EEXIST: file already exist

See original GitHub issue

Is there an existing issue for this?

I have searched the existing issues

Current Behavior

Something went wrong: Error: EEXIST: file already exists, mkdir ‘c:\Users\mulya\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vscode-vibrancy-runtime-v6’

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS:Windows 11
- VSCode:1.73.1
- Extension: 1.1.9

Anything else?

Screenshot 2022-11-11 185140 this happens when i reload vibrancy. Do you know how to solve this?

Issue Analytics

State:
Created 10 months ago
Comments:10 (5 by maintainers)

Top GitHub Comments

1reaction

illixioncommented, Nov 22, 2022

Hi. Haven’t seen this error before, Vibrancy is supposed to delete the existing runtime folder before copying the newest version upon running the reload action, but in your case the folder wasn’t deleted for some reason. Perhaps it’s a permission issue, though it should’ve generated a different error if that’s the case. Could you please try going to c:\Users\mulya\AppData\Local\Programs\Microsoft VS Code\resources\app\out and deleting the vscode-vibrancy-runtime-v6 folder manually, then trying the Reload Vibrancy action again?

This is a bug of the new version. This bug will reappear every time the configuration is modified. My Environment is the same as the publisher of this issue.

Can confirm that this was a bug, for some reason the fs module on Windows can’t remove folders that aren’t empty, switched to a rimraf library that seems to work properly.

1reaction

SuperManitocommented, Nov 20, 2022

Hi. Haven’t seen this error before, Vibrancy is supposed to delete the existing runtime folder before copying the newest version upon running the reload action, but in your case the folder wasn’t deleted for some reason. Perhaps it’s a permission issue, though it should’ve generated a different error if that’s the case.

Could you please try going to c:\Users\mulya\AppData\Local\Programs\Microsoft VS Code\resources\app\out and deleting the vscode-vibrancy-runtime-v6 folder manually, then trying the Reload Vibrancy action again?

This is a bug of the new version. This bug will reappear every time the configuration is modified. My Environment is the same as the publisher of this issue.