I’m getting a surprise

11:53:26.12 [ERROR] 1 Exception encountered:

Engine traceback:
  in `run` goal

IntrinsicError: No such file or directory (os error 2)

using

pants_version = "2.16.0.dev5"

Appreciate this might be a sharp edge of not being on a release version, but thought I’d ask since I didn’t spot any related issues. Seems to happen intermittently without an obvious trigger - and doesn’t happen with

scie_pants

which I’m probably going to push everyone on the team to use instead to solve 🙂

I'm getting something similar when running 2.17, albeit that's even more bleeding edge. I was hoping to take a look today

@chilly-holiday-77415 Are you able to roll back the pants_version to the most recent version that doesn't throw that error? Might give a starting point for some bisecting

unhelpfully, it’s fixed by changing to 7 and then back to 5 - so I assume re-initializing the scheduler is fixing whatever breaks

I had an inkling feeling that the daemon might also have a play in this. If I'm not mistaken it isn't restarted when switching to scie-pants

2.16.0.a0

is out. I would recommend not using the dev releases anymore, now that the alpha is available.

Switching back and forth between

./pants

and

pants

will restart the daemon. They both pass different injected args / env to the pants console script they both install.

That's certainly the expectation. I thought I saw otherwise though. Let me try it this morning and we can find out if I'm hallucinating or not

You know better than I then! I had to add a set -x to the

./pants

script and run

pants

with

RUST_LOG=trace

to re-learn if this was true!

Ahh right, I think I remember now what I was mis-remembering. I was accidentally using

pants

from muscle memory over in the pants repo in my work repo, which isn't valid yet because I have hacks in

./pants

. And precisely because it was invalidating the daemon my hacks weren't applied.