ripe-kitchen-64238
02/03/2023, 9:09 AMenough-analyst-54434
02/03/2023, 1:00 PMripe-kitchen-64238
02/03/2023, 1:08 PMenough-analyst-54434
02/03/2023, 1:17 PMfresh-needle-7063
02/03/2023, 1:28 PM.netrc
file for auth ok 👍
Two causes for my confusion:
• me trying with good/bad auth resulted in some temporary/partial blocks from our PyPI so it failed and appeared to not use the good auth when available 🤦♂️
• when then trying a negative test, removing the auth I had some weirdness with pants caching, even after removing the .cache/pants dir I still was able to use existing cached libs - until killing the pantsd (which I did not know was there 🤔 )enough-analyst-54434
02/08/2023, 3:08 PM.cache/pants/lmdb*
) but the result of all functions calls (@rules) are also memoized for the life of a single pantsd run in-memory. So, while pantsd is up and running Pants caches the most steps possible. It had already done a resolve with auth so it did not try again since it does not track the ~/.netrc
file outside the repo.fresh-needle-7063
02/08/2023, 4:00 PMenough-analyst-54434
02/08/2023, 4:13 PM~/.netrc
ideally, but its a 3rdparty tool (Pip via Pex) that reaches out and reads that file; so Pants would have to know about that reach-behind (which it does since we're talking about it!), and do something about it. Currently Pants has the idea that it only tracks files in the subtree its being used in somewhat baked in (IIUC / IIRC); so this is a bit of work / new ground.~/.netrc
would not be available (until that dependency were made explicit, in which case pants would track the file and this staleness bug would no longer exist).