github.com/lestrrat-go/jwx/v2@v2.0.21/.aspect/bazelrc/correctness.bazelrc (about)

     1  # Do not upload locally executed action results to the remote cache.
     2  # This should be the default for local builds so local builds cannot poison the remote cache.
     3  # It should be flipped to `--remote_upload_local_results` on CI
     4  # by using `--bazelrc=.aspect/bazelrc/ci.bazelrc`.
     5  # Docs: https://bazel.build/reference/command-line-reference#flag--remote_upload_local_results
     6  build --noremote_upload_local_results
     7  
     8  # Don't allow network access for build actions in the sandbox.
     9  # Ensures that you don't accidentally make non-hermetic actions/tests which depend on remote
    10  # services.
    11  # Developers should tag targets with `tags=["requires-network"]` to opt-out of the enforcement.
    12  # Docs: https://bazel.build/reference/command-line-reference#flag--sandbox_default_allow_network
    13  build --sandbox_default_allow_network=false
    14  test --sandbox_default_allow_network=false
    15  
    16  # Warn if a test's timeout is significantly longer than the test's actual execution time.
    17  # Bazel's default for test_timeout is medium (5 min), but most tests should instead be short (1 min).
    18  # While a test's timeout should be set such that it is not flaky, a test that has a highly
    19  # over-generous timeout can hide real problems that crop up unexpectedly.
    20  # For instance, a test that normally executes in a minute or two should not have a timeout of
    21  # ETERNAL or LONG as these are much, much too generous.
    22  # Docs: https://bazel.build/docs/user-manual#test-verbose-timeout-warnings
    23  test --test_verbose_timeout_warnings
    24  
    25  # Allow the Bazel server to check directory sources for changes. Ensures that the Bazel server
    26  # notices when a directory changes, if you have a directory listed in the srcs of some target.
    27  # Recommended when using
    28  # [copy_directory](https://github.com/aspect-build/bazel-lib/blob/main/docs/copy_directory.md) and
    29  # [rules_js](https://github.com/aspect-build/rules_js) since npm package are source directories
    30  # inputs to copy_directory actions.
    31  # Docs: https://bazel.build/reference/command-line-reference#flag--host_jvm_args
    32  startup --host_jvm_args=-DBAZEL_TRACK_SOURCE_DIRECTORIES=1
    33  
    34  # Allow exclusive tests to run in the sandbox. Fixes a bug where Bazel doesn't enable sandboxing for
    35  # tests with `tags=["exclusive"]`.
    36  # Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_exclusive_test_sandboxed
    37  test --incompatible_exclusive_test_sandboxed
    38  
    39  # Use a static value for `PATH` and does not inherit `LD_LIBRARY_PATH`. Doesn't let environment
    40  # variables like `PATH` sneak into the build, which can cause massive cache misses when they change.
    41  # Use `--action_env=ENV_VARIABLE` if you want to inherit specific environment variables from the
    42  # client, but note that doing so can prevent cross-user caching if a shared cache is used.
    43  # Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_strict_action_env
    44  build --incompatible_strict_action_env
    45  
    46  # Propagate tags from a target declaration to the actions' execution requirements.
    47  # Ensures that tags applied in your BUILD file, like `tags=["no-remote"]`
    48  # get propagated to actions created by the rule.
    49  # Without this option, you rely on rules authors to manually check the tags you passed
    50  # and apply relevant ones to the actions they create.
    51  # See https://github.com/bazelbuild/bazel/issues/8830 for details.
    52  # Docs: https://bazel.build/reference/command-line-reference#flag--experimental_allow_tags_propagation
    53  build --experimental_allow_tags_propagation
    54  fetch --experimental_allow_tags_propagation
    55  query --experimental_allow_tags_propagation
    56  
    57  # Do not automatically create `__init__.py` files in the runfiles of Python targets. Fixes the wrong
    58  # default that comes from Google's internal monorepo by using `__init__.py` to delimit a Python
    59  # package. Precisely, when a `py_binary` or `py_test` target has `legacy_create_init` set to `auto (the
    60  # default), it is treated as false if and only if this flag is set. See
    61  # https://github.com/bazelbuild/bazel/issues/10076.
    62  # Docs: https://bazel.build/reference/command-line-reference#flag--incompatible_default_to_explicit_init_py
    63  build --incompatible_default_to_explicit_init_py