Out of interest, is there a default timeout for

pantsd

, or will it keep running indefinitely until some change requires a restart?

Infinity and beyond. Anytime you change a global option (as you noted - pants.toml), it'll restart. There are also global options you can pass in at the command line which would cause the same. Hopefully some upcoming changes can reduce that startup time slightly. But yeah, it'll live forever functionally - unless I think the .pantsd folder is deleted

Great to know, thanks for the explanation!

No

Ah! I think I've found the issue. I've been alternating calls to

pants package

and

pants dependencies

. I ran the former with

-ldebug

but the latter at regular info level. I think this difference in logging level was what triggered the daemon restart.

I've done exactly the same thing more times than I care to admit 😊

Probably a silly question, but is there a specific reason why a log level change requires a daemon restart?

I can't answer that past it being a global option

Yeah, fair enough

More specifically, a "bootstrap option"

do we maintain a list of bootstrap items? I can't recall a time I've edited pants.toml and not had it restart the scheduler

Yes, and also not all global-scope options are bootstrap options

do we maintain a list of bootstrap items?

@wide-midnight-78598 there's a bootstrap options type https://github.com/pantsbuild/pants/blob/f8b6c4266eb3a94afec41c076e71843c62bad054/src/python/pants/option/global_options.py#L825-L833 that's inherited by the GLOBAL scope options: https://github.com/pantsbuild/pants/blob/f8b6c4266eb3a94afec41c076e71843c62bad054/src/python/pants/option/global_options.py#L1781-L1785

🎉 TIL