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
After upgrading to Nx 20 (from 19), and enabling the new database-based caching by removing the useLegacyCache flag from my nx.json, most (but not all) of my CIPE runs are failing with error that look like this:
Agent 'job-67292d4f767f6f3d87a1cbad-0-agent-2' exited with the error: Missing field code.
One of my team members was able to reproduce this issue locally, and when running with --verbose he obtained the following stack trace:
Error: Missing field `code`
at DbCache.applyRemoteCacheResults (.../node_modules/nx/src/tasks-runner/cache.js:80:27)
at DbCache.get (.../node_modules/nx/src/tasks-runner/cache.js:65:22)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async TaskOrchestrator.applyCachedResult (.../node_modules/nx/src/tasks-runner/task-orchestrator.js:131:30)
at async Promise.all (index 0)
at async TaskOrchestrator.applyCachedResults (.../node_modules/nx/src/tasks-runner/task-orchestrator.js:126:21)
at async TaskOrchestrator.applyFromCacheOrRunTask (.../node_modules/nx/src/tasks-runner/task-orchestrator.js:219:40)
at async TaskOrchestrator.executeNextBatchOfTasksUsingTaskSchedule (.../node_modules/nx/src/tasks-runner/task-orchestrator.js:85:13)
at async Promise.all (index 2)
at async TaskOrchestrator.run (.../node_modules/nx/src/tasks-runner/task-orchestrator.js:61:9)
This was with Nx 20.0.7, but as I said, it seems to be somewhat intermittent. Some of our CIPE runs went just fine, but many failed. Adding useLegacyCache: true back into the nx.json stopped this issue completely, so it appears to be related to the new caching.
I also have a support ticket open which contains more information, including a link to a CIPE.
Due to the following issue nrwl/nx#28806, which we encounter in the GitHub Window Unit Test Job regularly, we have to opt-in to NX's legacy cache mechanism. That will use the file system instead of a file DB for caching.
Due to the following issue nrwl/nx#28806, which we encounter in the GitHub Window Unit Test Job regularly, we have to opt-in to NX's legacy cache mechanism. That will use the file system instead of a file DB for caching.
Current Behavior
After upgrading to Nx 20 (from 19), and enabling the new database-based caching by removing the
useLegacyCache
flag from mynx.json
, most (but not all) of my CIPE runs are failing with error that look like this:One of my team members was able to reproduce this issue locally, and when running with
--verbose
he obtained the following stack trace:This was with Nx 20.0.7, but as I said, it seems to be somewhat intermittent. Some of our CIPE runs went just fine, but many failed. Adding
useLegacyCache: true
back into thenx.json
stopped this issue completely, so it appears to be related to the new caching.I also have a support ticket open which contains more information, including a link to a CIPE.
Nx Report
Node : 22.11.0
yarn : 4.5.1
nx : 20.0.7
@nx/js : 20.0.7
@nx/jest : 20.0.7
@nx/eslint : 20.0.7
@nx/workspace : 20.0.7
@nx/angular : 20.0.7
@nx/devkit : 20.0.7
@nx/eslint-plugin : 20.0.7
@nx/nest : 20.0.7
@nx/node : 20.0.7
@nx/web : 20.0.7
@nx/webpack : 20.0.7
typescript : 5.4.5
Package Manager Version
yarn 4.5.1
Operating System
The text was updated successfully, but these errors were encountered: