patternfly / patternfly/patternfly-react
Bug - CI/Build - Upgrade to node v20 has introduce a caching issue
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 862
- Forks
- 392
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 9
Description
Describe the problem
There is a bug in the latest release of node (https://github.com/nodejs/node/issues/51555) where occasionally the CI will fail. A work around for now is to disable the cache as was done in PR #10330 . We should reenable the caching once the fix has been addressed in a future update of node 20 LTS.
Is this issue blocking you?
No
What is your environment?
- CI only. This is not repeatable locally.
Jira Issue: PF-80
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review PR #10330 to identify where CI caching was disabled, then check the Node.js issue linked in this report and the current Node 20 LTS status. Done means re-enabling the cache after the upstream fix is available and confirming that CI completes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100