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 console extension always fails to build graph when changing the file tree #2091
Comments
It would be great if you could provide some logs or any of the information we ask for when filing a bug.
|
@MaxKless just did, thanks |
It would be great if you could provide some logs.
What do you mean by 'permanently fails'? What issues are you seeing? Is the project view not showing projects anymore? Is the graph/PDV view empty? Anything else? |
now I tried to reproduce the error with jest config and it doesn't happen, i will try to detect this situation again and will update with a log |
Okay thanks, I've seen this issue before it's good to have another report. |
Sure,
|
Do you have more than just that snippet? I'm specifically looking for things that mention file watching. The full logs help me get a better image of where things go wrong |
yes that sounds like an issue with file watching. Would you mind pasting your full logs from |
I've replaced
|
Did you try to reload window? |
I'm removing the |
I'm working on some changes to make Nx Console more resilient to changes like this :) |
@MaxKless
The copy paste error:
The Daemon is having a hard time keeping track of files. I'm on Ubuntu 22.04.4 |
can you try adding this to your .env It should fix this error and will be default behaviour in the future. |
That didn't quite do the trick @MaxKless :( |
@MaxKless The
Looking at the daemon.log file it looks like the daemon crashes when trying to create the project graph and then when you run a command after it gets stuck with a bad project graph.
|
thanks for checking it out. After setting the env variable, did you run nx reset & restart VSCode? |
The env is still set and verified to be active in the env, restarted code/computer multiple times, and nx reset at least 20 times due to it crashing. |
That makes sense because the env var is handled only in later versions... my bad, forgot to check. |
Hi! I have noticed that nx console extension permanently fails if file tree is changed.
Just for example - it's enough just to delete some JS file like jest.preset.js and it's already enough for the extension to stop working.
What is interesting - nx command line stays working normally.
WHat helps - is VS Code reloading, which is not really convenient.
Could you please check why it happens - it seems like the extension have some internal caching and it doesn't really catch file changes.
Thanks!
The text was updated successfully, but these errors were encountered: