-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
nx reset --only-workspace-data (nx 9.2.x - 9.5.1) => Failed to reset the Nx workspace #27006
Comments
End task all processes "Node.js" OR "VSCode" OR "Git" in Task Manager |
@dadfarjs Is that the solution? Why is this happening in the first place? To your point, it works again after killing all VS Code instances via the Task Manager. But the second you run "npx nx reset" it glitches again. |
I am also experiencing this issue with Nx 9.5.1. I tried downgrading to 9.5.0 the lowest version that supports Angular 18 and is not beta. Same thing. This is a show stopper for me just at the time that I wanted to migrate to Nx. My bad luck. Hopefully this gets resolved quickly. |
If there is a problem in one of the programs of your project and the "nx serve app-name" command is executed. This information will be placed in the workspace. You can use this command to see the program's problems in the terminal output: |
I checked nx by versions |
I have the same problem. Unfortunately - this is another bug that makes work terribly unpleasant. It has been practically constant for some time. I hope Team NX will improve the flow of releasing new versions, because it is getting worse and worse |
Hey! It might be a bug in Nx Console, the vscode extension. Can you close all instances of vscode & make sure processes are dead. |
NX Report complete - copy this into the issue template Node : 20.15.1 nx (global) : 19.4.4
|
I did some digging in the codebase and PRs introduced between versions 19.4.4 (that works ok) and 19.5.0 and it seems that the problem is with this PR: #26888 Also, checking Task Manager processes you can see that there are extra 4 node processes started and not killed after running e.g. Setting env variable mentioned in the PR to false makes all work ok again, i.e. setting NX_ISOLATE_PLUGINS=false e.g. in .env file of your repo. So either that PR should be reverted and previous default for plugin isolation used (i.e. not to use that plugin isolation), or there is a need of fixing internal logic of plugin isolation feature that currently makes versions 19.5.0+ completely unusable (at least on Windows). |
I also experienced this issue on 19.5.2 |
Error: EPERM: operation not permitted, open 'C:\Users\henke\Documents\prog\...\.nx\workspace-data\d\daemon.log' |
I encountered the same issue, but I managed to resolve it by following these steps:
After performing these steps, the issue was resolved. |
Thanks everyone for helping out and investigating here. The issue seems to be plugin isolation. We now spawn an isolated worker process for each plugin during project graph creation. |
While there's still no fix: you can disable plugin isolation for now using |
hey everyone! Just wanted to let you know that we've disabled plugin isolation on windows by default with |
Thank you, 19.5.4 works! |
Hey @MaxKless, I wanted to chime in, I have the same issue on Mac so it's not only related to widows. Disabling plugin isolation fixes the issue also on my side. I have both local nx plugins (aka ts files in the repo, referenced with a path in nx.json) and plugins loaded via npm ( Let me know if there is some way I can help on this issue Edit: I found a similar issue, probably related : #27040 |
This should be fixed by #27317, which was just merged. A new canary will go out tonight, if a few folks could try it and make sure things are working that would be appreciated. I'm going to preemptively close this out since the PR has been merged. If it is still broken, please let us know here or by opening a new issue. Thanks for the cooperation everyone :) |
Current Behavior
Resetting:
NX Failed to reset the Nx workspace.
Failed to clean up the workspace data directory.
Expected Behavior
nx reset
This might take a few minutes.
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
No response
Package Manager Version
npm --version 9.7.2
Operating System
Additional Information
nx 9.5.1
![no_security](https://private-user-images.githubusercontent.com/103028071/350412540-b511f387-2998-42f8-9955-f5b6be285af3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU1OTMxNDAsIm5iZiI6MTcyNTU5Mjg0MCwicGF0aCI6Ii8xMDMwMjgwNzEvMzUwNDEyNTQwLWI1MTFmMzg3LTI5OTgtNDJmOC05OTU1LWY1YjZiZTI4NWFmMy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTA2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwNlQwMzIwNDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01YmE1M2VhMTM3ZDg2OWM0Yzk3OWRiYTE3MDZmMTE1MGY1MzlhOGUzZDEyODhlNDdiZDZiZWEwYWM4ZGQ0OThlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.zCCYVJiE-bp1zL4cLDA3hS7IxlXkfWTuZzqAz8iyFMM)
nx 9.1.2
![with_security](https://private-user-images.githubusercontent.com/103028071/350413121-3c215fbf-8c70-4ada-8205-643a5217d0aa.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU1OTMxNDAsIm5iZiI6MTcyNTU5Mjg0MCwicGF0aCI6Ii8xMDMwMjgwNzEvMzUwNDEzMTIxLTNjMjE1ZmJmLThjNzAtNGFkYS04MjA1LTY0M2E1MjE3ZDBhYS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTA2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwNlQwMzIwNDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lNzliMDhhMDgxNjExNzFkZmVlZjMxY2I2OTg1NjE2NzgzNDJiZDI4YjVkOWZmMGI5Y2VmMzZhYTc2MjJiNzQ1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.3MK-5e2NL5UU0tHlzsEP0StaacahMdgb_0gWaYMva0E)
The text was updated successfully, but these errors were encountered: