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
We are seeing this spurious error a lot. It's unclear what the cause it, but it seems to happen especially when there are a lot of affected files (i.e. change to root package.json). This has been going on basically ever since we use nx it feels (since the 16.x days).
This happens only during "git commit". We are using the pre-commit package to run "nx affected --target=build".
I'm just opening this issue to see if errors see this too. It seems to be a combination of pre-commit and nx, but what exactly is unclear, as the message comes from nx.
We do confirm this issue. It is happening when running NX commands concurrently which are touching the cache. As they are not synchronized between each other they tend to clash on the current state.
We noticed to issues "os error 2" and "os error 66"
Error 2: can be easily fixed by checking if the path exist before deleting it
Error 66: Is about deleting a folder that has content inside. NX team would need to verify if this is intended if so either force remove it, or do nothing.
Current Behavior
We are seeing this spurious error a lot. It's unclear what the cause it, but it seems to happen especially when there are a lot of affected files (i.e. change to root package.json). This has been going on basically ever since we use nx it feels (since the 16.x days).
This happens only during "git commit". We are using the pre-commit package to run "nx affected --target=build".
I'm just opening this issue to see if errors see this too. It seems to be a combination of pre-commit and nx, but what exactly is unclear, as the message comes from nx.
Typical output looks like:
Expected Behavior
Running nx by itself works fine.
GitHub Repo
No response
Steps to Reproduce
We don't really now.
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: