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
In not very stable fs environments (mounted cache directory with NFS based volume) there are sometimes failures on atomic fs operations. Ideally these should be handled (when possible) and the actual task run should not exit with failure.
Expected Behavior
Failure to write latest cache hash should be reported but it should not make the task run exit with failure.
Would it be enough to wrap writeToFile into try/catch? Could it potentially break something on workspace? Or is it just that latest cache hash entry will be missing?
Steps to Reproduce
Have unstable fs, or
Mock fs import to fail.
Failure Logs
Environment
> NX Report complete - copy this into the issue template
Node : 14.17.5
OS : darwin x64
npm : 6.14.14
nx : Not Found
@nrwl/angular : 12.9.0
@nrwl/cli : 12.9.0
@nrwl/cypress : 12.9.0
@nrwl/devkit : 12.9.0
@nrwl/eslint-plugin-nx : 12.9.0
@nrwl/express : Not Found
@nrwl/jest : 12.9.0
@nrwl/linter : 12.9.0
@nrwl/nest : 12.9.0
@nrwl/next : Not Found
@nrwl/node : 12.9.0
@nrwl/nx-cloud : Not Found
@nrwl/react : Not Found
@nrwl/schematics : Not Found
@nrwl/tao : 12.9.0
@nrwl/web : Not Found
@nrwl/workspace : 12.9.0
@nrwl/storybook : 12.9.0
@nrwl/gatsby : Not Found
typescript : 4.3.5
The text was updated successfully, but these errors were encountered:
…sh cache files (#6959)
* fix(core): wrap writing cache hash into try/catch
Instead of failing the task run process it will allow the process to continue.
Fixes of #6957
* fix(core): ignore errors writing latest output hash cache files
Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
Current Behavior
In not very stable fs environments (mounted cache directory with NFS based volume) there are sometimes failures on atomic fs operations. Ideally these should be handled (when possible) and the actual task run should not exit with failure.
Expected Behavior
Failure to write latest cache hash should be reported but it should not make the task run exit with failure.
Would it be enough to wrap writeToFile into
try/catch
? Could it potentially break something on workspace? Or is it just that latest cache hash entry will be missing?Steps to Reproduce
Failure Logs
Environment
The text was updated successfully, but these errors were encountered: