Is there a reason why pants' limit on concurrent runs applies to the

help

command?

Good question, Stu would know best and is out today. but my limited understanding is that we might be able to work around that; I think

help

early exits Would you be willing to open a ticket? https://github.com/pantsbuild/pants/issues/new/choose If it's not very easy to do, the answer would likely be to lean into https://github.com/pantsbuild/pants/issues/7654

+1, I wish it got more votes in the 2022 survey. Altho as explained at https://blog.pantsbuild.org/the-2022-annual-community-survey-is-a-wrap-and-the-results-are-in/ the votes aren't literal gospel and maintainers may prioritize things like this

@loud-laptop-17949 we’re using multiple processes using

PANTS_CONCURRENT=True

. You can enable this via

pants.toml

as mentioned here: https://www.pantsbuild.org/docs/reference-global#section-concurrent

setting

--concurrent

will disable

pantsd

, so you should probably not set it globally in your repository. it’s intended more as a localized “please run this command concurrently” flag, rather than something that you put in

pants.toml

sorry for the confusion there: the end goal is to deprecate the

--concurrent

flag by allowing concurrent runs, but we wanted something with a different semantic meaning than

--no-pantsd

, so that users could track why they were skipping pantsd.