a year ago
We often encounter a cache issue with yarn install. Redeploy would work but it feels unreliable and requires us to monitor the builds. It happens to many nodejs projects. Is there a way to avoid this issue?
5 Replies
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Hi @melissa, this issue has occurred quite a lot today. Below are some examples
a70dc0fb-87e3-4105-aedb-b05f8e0d24cd
6d99299a-0dec-4058-8fdf-a6c8009a1813
689cbd5d-4960-4aa9-a882-de3fe43f0d3c
124fdf2d-6d7e-4fe2-b112-7a1057f6345f
Status changed to Awaiting Railway Response Railway • over 1 year ago
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Thanks for providing examples, we'll take a look
Hi @david, any update on this?
Status changed to Awaiting Railway Response Railway • over 1 year ago
a year ago
Hello,
After some online research this seems to be a common issue with yarn, and thus far outside of our control.
And thus unfortunately the only options I can give would be to disable cache with a NIXPACKS_NO_CACHE=1 service variable, or switch to a package manager that doesn't exhibit such issues.
Status changed to Awaiting User Response Railway • over 1 year ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago