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
Running certain commands on nx 20.1.0 gives a "Could not execute command because the task graph has a circular dependency" error, even though there aren't actually any circular dependencies.
Expected Behavior
Running nx commands should complete successfully.
GitHub Repo
No response
Steps to Reproduce
As best as I can tell these are the reproduction steps:
Run nx reset
Run a cachable command that depends on other packages (I'm using npx nx run-many --target=build --all where build has "dependsOn": ["^build"]).
Run nx reset again, leaving the build outputs alone
Run build again.
On the second invocation of build with a clean cache and existing outputs it will falsely think there is a circular dependency. Also when trying to make a minimal repro of this issue I found that it stops happening for me if I remove the files in .github/ISSUE_TEMPLATES. Which is exceedingly strange. I unfortunately haven't yet found a full minimal reproduction, but I can consistently reproduce it locally in our full (private) workspace.
Here is the script I ran that reliably reproduced the issue:
I bisected the nx version and v20.1.0 is the first release with this issue.
I also tried to debug this locally by cloning the nx repo, but I was unable to figure out how to run the locally-built nx on the failing project. If you can provide instructions on how to make that work I'd be happy to look into this further myself.
The text was updated successfully, but these errors were encountered:
Current Behavior
Running certain commands on
nx
20.1.0 gives a "Could not execute command because the task graph has a circular dependency" error, even though there aren't actually any circular dependencies.Expected Behavior
Running
nx
commands should complete successfully.GitHub Repo
No response
Steps to Reproduce
As best as I can tell these are the reproduction steps:
nx reset
npx nx run-many --target=build --all
wherebuild
has"dependsOn": ["^build"]
).nx reset
again, leaving the build outputs alonebuild
again.On the second invocation of
build
with a clean cache and existing outputs it will falsely think there is a circular dependency. Also when trying to make a minimal repro of this issue I found that it stops happening for me if I remove the files in.github/ISSUE_TEMPLATES
. Which is exceedingly strange. I unfortunately haven't yet found a full minimal reproduction, but I can consistently reproduce it locally in our full (private) workspace.Here is the script I ran that reliably reproduced the issue:
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
I bisected the
nx
version and v20.1.0 is the first release with this issue.I also tried to debug this locally by cloning the
nx
repo, but I was unable to figure out how to run the locally-builtnx
on the failing project. If you can provide instructions on how to make that work I'd be happy to look into this further myself.The text was updated successfully, but these errors were encountered: