Is there any way to see what triggered this change

10:59:31.12 [INFO] Remote cache/execution options updated: reinitializing scheduler...

?

.pants.d has a log file in it (pants.log I think) probably a place to start looking.

Can you share the

./pants

commands you were running? Did any sources of config options change? CLI, env, pants.toml?

that line is caused by the remote execution token expiring

ok, so if I don't run a command for 40 minutes, the token will expire leading to needing to acquire a new token and re-initialize?

as it stands, yes… that’s a function of the token expiration time, and Toolchain sets 40 minutes.

this re-inits the local scheduler too right?

there are definitely paths forward for fixing that issue

that would explain some of what I am seeing

@polite-garden-50641 is that correct that Toolchain is not extending the life of short-lived tokens upon use?

I have no reason to believe it is not, I have no idea at all

we don't extend tokens in the server upon use... the toolchain plugin allows pants to refresh the token, not sure if that is implemented on the pants side or not. the token TTL if the remote cache permission is requested is 45min.