I'm finding quite frequently that pants commands e.g.

pants test

get stuck shortly after starting. They start up but then nothing else prints to stdout and the command just hangs indefinitely. I just see something like

⠂
⠒
⠒
⠒
⠒
⠒
⠒
⠒
⠒
⠒
⠒
⠒
⠒
⠒

Trying again usually works but this is happening quite often.

Anything in the logs>

what logs would i check for this kind of issue?

Checking whatever's in the .pants.d logs maybe, to see if there are any errors there. Also, before deleting the pids directory, checking if pants --no-pantsd works would be interesting

--no-pantsd does indeed fix the issue too

"fix" - it's basically just running without the daemon, and deleting pids is just restarting the daemon I just wanted to verify, as anything else would be horrifically broken

Got it, pantsd seems to cause a lot of trouble for me

It's generally been stable for me for a couple years. But when it fails, it fails spectacularly. Was there anything in the logfiles (like in pants.d/workdir)?

I wasn't really sure what to check exactly and didn't spend much time digging yet. I did see a lockfile there. i have been getting claude code to run pants commands recently and maybe that's putting things into a bad state.