PiperOrigin-RevId: 792784366
Change-Id: Iad8177669b68b4f8ee632839a99082e7a193d9e2

the value of the flag seems to be no longer used

PiperOrigin-RevId: 792662960
Change-Id: I1057b4fb5e837a74c051967740b3eb3d5b0ff6fd

PiperOrigin-RevId: 792651764
Change-Id: I172c5bd194508df3c58c9a8f3666ff6cd4d0520f

PiperOrigin-RevId: 792634757
Change-Id: I0fe46233e78e30ce1fee7818aca8ff0c991969ba

PiperOrigin-RevId: 792622748
Change-Id: Id3cda96446b70a191664f5ab32c7185a37d4fd64

The remaining test in BazelProtoLibraryTest are more adequate for integration testing than unit testing.

PiperOrigin-RevId: 792567553
Change-Id: I098534d30ec5a7d46485c26f93b2e5ed0c53892b

PiperOrigin-RevId: 792537906
Change-Id: Ifb0346c2bc9955796f9c74cca1ab881788105919

PiperOrigin-RevId: 792533001
Change-Id: Id9bcb6fda32207c0a8f78ee6f1abd4b95c92ee94

PiperOrigin-RevId: 792532654
Change-Id: If47311fa3799582e0138208c7d5e32159386f19a

PiperOrigin-RevId: 792529880
Change-Id: I3cda5b3ab9b7b2dc8ce6a5d6d19120d3f9b8a4d0

The default comparator for `PathFragment` may sort unrelated paths between a path and a child path, which results in `contains` behaving incorrectly as soon as paths such as `foo/bar` and `foo/bar-baz` are present in the set. This is a bug introduced by #26639.

This is fixed by introducing a new `Comparator` for `PathFragment` that sorts `/` lower than any other character. This will also be used in future work on #21378 and is thus placed in `PathFragment`. It may become the default in the future, but not until Blaze has been confirmed to not rely on the order.

Closes #26714.

PiperOrigin-RevId: 792519419
Change-Id: I8bf8fc6b15cc5bcf0d303057a828fbd644032bab

command_failure_utils - unlike the `command` target it was split from - doesn't
depend on devtools/build/lib:shell (and, in turn, unix_jni); this breaks the
unnecessary dependency chain between e.g. package_options and unix_jni.

Pointed out by nharmata@ in discussion of b/437155683.

PiperOrigin-RevId: 792474304
Change-Id: I45f38f4ad0b6b21d23b0ff9fd40312cad96ed958

This significantly reduces the transitive dependencies of the Starlark json module,
and, transitively, of Bazel's Starlark interpreter.

Also take the opportunity to remove unused build dependencies in affected targets.

PiperOrigin-RevId: 792415905
Change-Id: Ic9b6a67d1dc7591c6daac6e5369ccea6e4d08c3f

This makes it easier to understand what kinds of exceptions can be thrown by a particular function and avoids wrapping in `RuntimeException` that can turn regular failures into crashes.

In particular, this resolves an issue seen on a PR in which `RemoteSpawnRunner` turned an `ExecException` raised by `RES.uploadInputsIfNotPresent` due to a lost input into a `RuntimeException`, thus resulting in a crash. It's not clear whether this behavior can also happen at HEAD or whether all callers unwrap the `RuntimeException`, so this change doesn't necessarily fix a bug.

Work towards #21378

Closes #26650.

PiperOrigin-RevId: 792329428
Change-Id: Iced921ce8633926e6488d38502c9b93c9fffa393

*** Reason for rollback ***

b/437115008

*** Original change description ***

Add experimental_managed_storage_service_table_name flag.

Updates the RemoteAnalysisCachingServicesSupplier.configure method
signature to include the buildId.

PiperOrigin-RevId: 792294579
Change-Id: I5c322101fb5578d14b252a75a3bac3cc2f2ba7b9

Baseline: b4216efd

Cherry picks:

   + bbfb288a:
     Fix
     https://github.com/bazelbuild/bazel/commit/9aa7583e97bffb17d2a6f4
     8aecefa932e8064daa performance regression.

Important changes:

  - Tool paths specified in `cc_toolchain` action configs are now
    normalized based on the current execution platform's OS rather
    than the host OS. In particular, Windows-style absolute paths are
    now treated as absolute paths when building on a Windows executor
    from a non-Windows host.

This release contains contributions from many people at Google, as well as Austin Schuh, Benjamin Peterson, Ed Schouten, Fabian Meumertzheim, George Gensure, Mike Lundy, Wade Carpenter.

For a package loaded with lazy macro expansion, Target.getPackage() returns null,
so we now need to use TargetProvider/PackageProvider to retrieve a target's
package's BUILD file target or to iterate sibling targets.

As a follow-up, we'd want to avoid unnecessarily loading full packages in
implementations of TargetProvider.getTarget() and in TargetLoadingUtil -
but that requires another new skyfunction.

Working towards https://github.com/bazelbuild/bazel/issues/23852

PiperOrigin-RevId: 792276714
Change-Id: I76266c10d4f5d6e087a6f38c6b6bfe06eb72603b

This makes it possible to debug config-dependent errors.

Closes #26690.

PiperOrigin-RevId: 792275177
Change-Id: I026d6aae8a3dbc1da20a155f4b873d0349b76a8d

Introduce --experimental_lazy_macro_expansion_packages and allow PackageFunction to assemble packages from package pieces

At present, lazy symbolic macro expansion is incompatible with any package that
calls native.existing_rule() or native.existing_rules() outside of a finalizer
symbolic macro, and so cannot be enabled globally.

Working towards https://github.com/bazelbuild/bazel/issues/23852

PiperOrigin-RevId: 792253787
Change-Id: Ifb1fc9f0259b188e2bf33f58cd0a2ec610362db2

Preparation for #25870

Closes #26698.

PiperOrigin-RevId: 792236653
Change-Id: Iaf10cc32c4938987a6afef1b73081666963435b2

This is needed to convert CcInfo to Starlark without causing a major regression.

Mark the field as legacy, because we'll need to eventually clean it up.
Upgrade rules_java, that support both old and new field location.

PiperOrigin-RevId: 792196604
Change-Id: I1b26336b6f234bd3cb123c213e68daee19c2e50f

PiperOrigin-RevId: 792195826
Change-Id: I23da70add656315a42c1e4ff3ec9573da494f78d

Updates the RemoteAnalysisCachingServicesSupplier.configure method
signature to include the buildId.

PiperOrigin-RevId: 792180638
Change-Id: I9bf023911c237d6c9bd936297789edbee155ad7a

This is mandated by the test encyclopedia, but HOME wasn't exported and isn't set by the test action.

Fixes #10652
Fixes https://github.com/bazel-contrib/rules_go/issues/4108

Closes #26697.

PiperOrigin-RevId: 792171303
Change-Id: I60297936a9562fb61ca7aca9bb9591ea86e8f5aa

configured by flag `--experimental_thread_dump_interval`.

The thread dumps can be found under `<output_base>/server/thread_dumps/`.

Dumps from last invocation are deleted at the start of the current invocation to avoid accumulating too much dumps in the output base.

RELNOTES: Added flag `--experimental_thread_dump_interval` to allow Bazel dump threads periodically.
PiperOrigin-RevId: 792131384
Change-Id: Ib9fe7a659f51bdd404a28229055441a6d3a87f3d

*** Reason for rollback ***

Apparently it is used: https://buildkite.com/bazel/google-rules-cc-presubmit/builds/1068#01988463-682d-4242-812f-3679cd9304d6

*** Original change description ***

Remove get_native_library_info_provider

It was unused.

PiperOrigin-RevId: 792118898
Change-Id: I265c98323b2fa5c417088343bda8e0f466924b35

PiperOrigin-RevId: 792107510
Change-Id: I0af3c73873b4313f92e26b064a455a2b2aadaa37

Empty directories that are regular inputs were already kept around during spawn input expansion, empty directories in runfiles weren't.

This was found while working on a "golden test" for Merkle tree computation that pins down the Merkle tree hash for a complex spawn. Since this hash is determined purely by the RBE spec, it makes sense to have a test that verifies Bazel's compatibility regardless of its particular RBE implementation. This will be used to catch regressions when changing to a new implementation.

Work towards #21378

Closes #26623.

PiperOrigin-RevId: 792086827
Change-Id: Iab0691582d785030ceac4970067dc709e7b9eb0d

which can dump both platform and virtual threads.

PiperOrigin-RevId: 792056803
Change-Id: I24acc50c0cb79edffb891d82e023e3df1228e6e7

Fixes https://github.com/bazelbuild/bazel-central-registry/pull/5457#issuecomment-3160351631

PiperOrigin-RevId: 792043107
Change-Id: I24476e994609ee8513879e6f44ffd199893c5cf2

PiperOrigin-RevId: 791860288
Change-Id: I44b442e6cd5b88078a6171259728b8d6f9c93703

No reason to reconstruct on every call.

PiperOrigin-RevId: 791769066
Change-Id: Ibcad64b635c8dd2edca24469ffb05e7556b696f8

This CL fixes a StringIndexOutOfBoundsException that occurs in FileDependencyDeserializer
when parsing a cache key where the Base64-encoded version string contains a / character.

The bug was caused by an incorrect assumption in how the parent directory was being
extracted from the cache key. The code used key.lastIndexOf('/') to find the end of the
parent directory path, but it did not account for cases where the last / was part of the
Base64-encoded version string, not the file path. This would lead to an invalid index being
passed to key.substring().

The fix corrects the logic to ensure that the search for the parent directory's trailing
slash is confined to the path portion of the key. This is done by checking that the found
index of the slash is greater than the starting index of the path.

PiperOrigin-RevId: 791767573
Change-Id: Ica4c40b53f7fb65e48e76c29118541a48175b585

It was unused.

PiperOrigin-RevId: 791721552
Change-Id: Ie63b399fbd876dea90e256c8ad77c91f7ae310fe

The test was ignored and wasn't passing after proto_library was ported to Starlark. The artifical dependency was never really needed.

PiperOrigin-RevId: 791657986
Change-Id: Id27cdd525c0ceed0defc7383c1ab1fd8f236f28c

PiperOrigin-RevId: 791587137
Change-Id: Ibf68e6cadd6fea983346728433a5d7c646b5b5c4

PiperOrigin-RevId: 791569843
Change-Id: I0c10511b56574df1f687689f2bea045712ad1631

In order to better support internal html report functionality.

PiperOrigin-RevId: 791299767
Change-Id: Idb601c0285fc290fac99100b3ead9eae89f98bb4

PiperOrigin-RevId: 791262254
Change-Id: Iadb2c83f64c2bd9cc8cb5a024b655dbeb9ce4489

PiperOrigin-RevId: 791241638
Change-Id: Iba10d0e6de3387f820acd73c0e9d24818cab1901