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 think I just managed to reproduce a situation when nx watch goes into an indefinite loop constantly running same task again and again.
It runs build command which is supposed to be cached ( and it is ) but DaemonSocketMessenger keeps receiving the information that file is changed and runs same command again.
Expected Behavior
It's ok if watch command listens for all files ( ideally I would prefer that watch can also accept somehow only certain files to watch, not for everything ) but even though it should not run the command again if file was processed ( target inputs are not changed and target result is cached )
On vacation now - will check when come. But from another side I don't want to ignore scripts, I think what happens - is that watch doesn't analyze inputs and outputs properly running task even if it's cached
Current Behavior
Hi! I think I just managed to reproduce a situation when nx watch goes into an indefinite loop constantly running same task again and again.
It runs build command which is supposed to be cached ( and it is ) but DaemonSocketMessenger keeps receiving the information that file is changed and runs same command again.
Expected Behavior
It's ok if watch command listens for all files ( ideally I would prefer that watch can also accept somehow only certain files to watch, not for everything ) but even though it should not run the command again if file was processed ( target inputs are not changed and target result is cached )
GitHub Repo
https://github.com/ThePlenkov/nx-plantuml
Steps to Reproduce
Preferably open repo in codespaces or make sure you have docker installed ( for command execution )
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: