Also, why does pants re-download so many of the go...
# general
p
Also, why does pants re-download so many of the go modules? Does it use the
~/go
cache? Does it use its own cache? Or are they really downloaded on every run?
l
It is somehow related to this issue -> https://github.com/pantsbuild/pants/issues/20274
pantsd
is responsible for caching but it gets killed due to OOM. At least this is my naive understanding of the problem šŸ™‚ Go backend is still experimental. You can read more here: • https://pantsbuild.slack.com/archives/C0D7TNJHL/p1704983879548679 • https://pantsbuild.slack.com/archives/C046T6T9U/p1702061530620109
šŸ‘ 1
c
https://github.com/pantsbuild/pants/pull/20552 specifically re cacheing if you didn't catch that in the cross-linking.
šŸŽ‰ 1