You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I recently tried out NX and was able to successfully run a command.
Afterwards the daemon does no longer respond. When I tail the logs of the daemon I can see the following:
[NX Daemon Server] - 2024-09-09T14:58:32.556Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.608Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.660Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.712Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.764Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.808Z - [REQUEST]: Updated workspace context based on watched changes, recomputing project graph...
[NX Daemon Server] - 2024-09-09T14:58:32.808Z - [REQUEST]: .nx/workspace-data/d/daemon.log,.nx/workspace-data/storybook.hash,.nx/workspace-data/project-graph.json,.nx/workspace-data/file-map.json,.nx/workspace-data/eslint-7836109672759906007.hash
[NX Daemon Server] - 2024-09-09T14:58:32.808Z - [REQUEST]: .nx/workspace-data/project-graph.json~6d38d8c7,.nx/workspace-data/file-map.json~6d38d8c7,.nx/workspace-data/file-map.json~5e810508,.nx/workspace-data/file-map.json~b7f082c2,.nx/workspace-data/project-graph.json~b7f082c2,.nx/workspace-data/project-graph.json~5e810508
[NX Daemon Server] - 2024-09-09T14:58:32.811Z - Time taken for 'hash changed files from watcher' 3.195973000001686ms
[NX Daemon Server] - 2024-09-09T14:58:32.816Z - [WATCHER]: 0 file(s) created or restored, 2 file(s) modified, 0 file(s) deleted
[NX Daemon Server] - 2024-09-09T14:58:32.868Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.920Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:32.972Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.024Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.076Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.128Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.180Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.232Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
[NX Daemon Server] - 2024-09-09T14:58:33.283Z - [WATCHER]: .nx/workspace-data/d/daemon.log was modified
I does this in a endless loop. When I stop the daemon I can run again one command and afterwards it is again in this loop.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I recently tried out NX and was able to successfully run a command.
Afterwards the daemon does no longer respond. When I tail the logs of the daemon I can see the following:
I does this in a endless loop. When I stop the daemon I can run again one command and afterwards it is again in this loop.
Anyone an idea what causes this problem?
My
nx.json
is pretty simple:Beta Was this translation helpful? Give feedback.
All reactions