Description of the problem / feature request:

The presence of a .bazelversion file that defines any non-matching version at the root of a directory structure prevents bazel from intepreting any commands in any subdirectory, including bazel version, help, info.

However, these are the commands needed to debug why .bazelversion is not satisfied, or to query non-build-related hel

specifically, 'PANTSD_REQUEST_TIMEOUT_LIMIT' (and more such environment variables, after merging #7913):

written:
https://github.com/pantsbuild/pants/blob/3898855f92700de10b35c2626e5df9893f6f9e54/src/python/pants/bin/remote_pants_runner.py#L139
read:
https://github.com/pantsbuild/pants/blob/3898855f92700de10b35c2626e5df9893f6f9e54/src/python/pants/pantsd/pailgun_server.py#L248

separatel

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

Bloop supports globs for source files since #1176.

The same should be done for resources.

For adding our repo to the upstream integration CI (tweag/rules_haskell#754, bazelbuild/continuous-integration#235) we need to pull many/all of our tests into bazel rules.

I’m pretty certain many of these can be implemented as simple sh_tests (or genrules) instead.