Jake Dern

Took the time this morning to try and reproduce this on my personal desktop and the same thing happens. I'm using wsl2 environment with ubuntu 20.04 in both cases. I...

Here's some basic version information from the second environment: 

As another data point, I cloned/installed on windows and cannot reproduce the issue. Perhaps is something with wsl2 environment specifically: In between each of these commands I made miscellaneous project.json...

Some last diagnostic points if it helps. I was able to reproduce this with nx 17.3.2 and nx 16.9.1 on wsl2 ubuntu 2004. Here are the daemon logs from when...

I made an interesting discovery. It seems that if you edit the file using vim or vi then this issue happens, if you don't then everything works fine. Things that...

Some more findings. Here's the log output from the daemon when editing the file with vscode (WORKS): ``` [NX Daemon Server] - 2024-02-24T04:14:19.933Z - Started listening on: /tmp/b20c1ae11e58f59ef244/d.sock [NX Daemon...

@AgentEnder I've identified the root cause of this problem. Basically everyone who uses an editor that creates a temp file and replaces the old one as a save strategy (vim/neovim...

My team is also running into this issue in Linux Dev Containers. Starting the daemon manually using `nx daemon --start` and/or adding `NX_DAEMON=true` to the environment does not restore the...

Here is our solution for working around this in devcontainers - We're hacking the daemon client with the following script on startup after running `npm install`. It's not perfect since...

Still an issue we're working around in our team. Commenting to stop it from being marked stale.