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
file F is the input of task Y and the output of task X
then the cache key for task Y appears to be computed using the contents of F prior to task X running, which can result in an incorrect cache hit if task X changes the contents of F.
Expected Behavior
The cache key for task Y should be computed using the contents of F after task X completes.
Run nx run foo:b2c a few times, until you see that the b2c task is hitting the cache.
Change the contents of foo/a.
Rerun nx run foo:b2c, and note that the b2c task is still hitting the cache, and that while foo/b has been updated to match the new contents of foo/b, foo/c still has its original contents.
Current Behavior
If
then the cache key for task Y appears to be computed using the contents of F prior to task X running, which can result in an incorrect cache hit if task X changes the contents of F.
Expected Behavior
The cache key for task Y should be computed using the contents of F after task X completes.
GitHub Repo
https://github.com/ethantkoenig/nx-cache-bug
Steps to Reproduce
nx run foo:b2c
a few times, until you see that theb2c
task is hitting the cache.foo/a
.nx run foo:b2c
, and note that theb2c
task is still hitting the cache, and that whilefoo/b
has been updated to match the new contents offoo/b
,foo/c
still has its original contents.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: