I am having trouble with the `export` goal that I can t seem

Question

I am having trouble with the `export` goal that I can t seem to figure out Earlier today I deleted my local pants caches and now when I run ` pants export resolve=default` the symlink in the dist directory links to a non existent directory in ~ caches Running ` pants export ` to export all resolves does not seem to have this problem

happy-kitchen-89482 · Answer

Which Pants version is this I think there were some fixes to this recently

loud-laptop-17949 · Answer

2 15rc2

happy-kitchen-89482 · Answer

Does this happen in 2 16 0 dev5

loud-laptop-17949 · Answer

i will try it tomorrow

loud-laptop-17949 · Answer

it seems maybe ok in 2 16

loud-laptop-17949 · Answer

let me go through another round of testing slow bc it requires deleting all the local caches

loud-laptop-17949 · Answer

yeah seems fine on 2 16 0 dev5 even with an empty cache

loud-laptop-17949 · Answer

usually deleting named caches will cause this problem

happy-kitchen-89482 · Answer

Cool I recall fixing some issues that seem related to this so maybe this is OK now fingers crossed

loud-laptop-17949 · Answer

Yeah but do we need to cherry pick something to the 2 15 branch I don t want to block 2 15 0 but getting something in 2 15 1 would be nice

loud-laptop-17949 · Answer

is this the fix in 2 16 <https github com pantsbuild pants pull 17849>

loud-laptop-17949 · Answer

I can try bisecting but testing is quite slow because it requires deleting the cache I think

happy-kitchen-89482 · Answer

I m not sure that s it specifically There were several changes to how export works I think this might have been fixed across that set of changes

happy-kitchen-89482 · Answer

Let me see if I can isolate a bugfix into 2 15 x

happy-kitchen-89482 · Answer

That symlinking logic does assume that the cache won t be pulled out from under it

happy-kitchen-89482 · Answer

I mean when creating the symlink we should verify that its target exists of course But if a user is in the habit of deleting the cache then they may do so after we create the symlink in which case we have no recourse

happy-kitchen-89482 · Answer

You could try and using the option to create a new venv instead of symlinking It will be slower but maybe not enough to matter

loud-laptop-17949 · Answer

yeah I tested that and it appears to work but for our default resolve its much much slower

loud-laptop-17949 · Answer

on a warm cache it goes form seconds to minutes

happy-kitchen-89482 · Answer

Yikes

happy-kitchen-89482 · Answer

That is enough to matter

happy-kitchen-89482 · Answer

Can you open a ticket with some exact repro steps and I ll root cause this and port just the fix to 2 15 x

loud-laptop-17949 · Answer

sure