When would we expect `experimental shell command` to rerun I

Question

When would we expect `experimental shell command` to rerun I m seeing it run essentially every daemon restart which isn t ideal thread

witty-crayon-22786 · Answer

cc < ancient vegetable 10556> ^

bitter-ability-32190 · Answer

I m using `build file dir` I would think that wouldn t do it though thinking face

witty-crayon-22786 · Answer

Chris identified this same bug about an hour ago and has started looking at it

bitter-ability-32190 · Answer

I can try anything out locally because I m currently using `pants from sources` and also I have a forked impl for `experimental shell command` in my repo stuck out tongue

bitter-ability-32190 · Answer

Last time I saw this it was an issue with using sets

bitter-ability-32190 · Answer

The debug log lines are the exact same thinking face

bitter-ability-32190 · Answer

It s weird too because it s actually running the command We don t hit the process cache either

witty-crayon-22786 · Answer

yea Chris determined that this might be a bug in Snapshot digests repro is on <https github com pantsbuild pants issues 16825 issuecomment 1311073810> i was going to look Monday

bitter-ability-32190 · Answer

With my track record recently it s probably related to symlinks sweat smile rolling on the floor laughing

witty-crayon-22786 · Answer

that was the first thing that came to mind yea the bisect was tricky because it required two ` no pantsd` builds per commit so i m not sure we know exactly when it was introduced but i ll probably just work it from the repro on `main`

witty-crayon-22786 · Answer

to close the loop on this one it was <https github com pantsbuild pants pull 17549|https github com pantsbuild pants pull 17549>