This option, which is different from the startup option of the same
name, has no effect and doesn't even show a warning, which can be
confusing.

Closes #24953.

PiperOrigin-RevId: 717853503
Change-Id: I8d7d1229f692007c4350b6c15526b7a95bbed5ef

Commit
https://github.com/bazelbuild/bazel/commit/79508becbb9195dc59e24b9aa3dbaf880c209e2e



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

... if the corresponding output is materialized afterwards and hasn't
been changed.

Failing to do so will cause an incremental build to re-check the action
cache for actions whose outputs were materialized during last build.
This can be very slow if the size of the outputs are large.

We achieved this by storing `FileContentsProxy` in the remote metadata
after materialization. During dirtiness check, we compare remote
metadata and the corresponding local metadata with their `digest`, or
`proxy` if `digest` is not available for local metadata,

A user reported back the wall time of their very first increment build
is improved by this change from `14s` to less than `1s` in common case,
and from `115s` to less than `1s` in worst case.
https://github.com/bazelbuild/bazel/issues/24763

PiperOrigin-RevId: 715734718
Change-Id: Id1a1a59d8b5f3e91a7ae05a73663ff37eee6d163

Fixes #24920.

PiperOrigin-RevId: 715819891
Change-Id: I1c2e582a3d4c6e87e5c76837abb7a175eed3e850 
(cherry picked from commit c570f978

)

Fixes #24933

Co-authored-by: Googler <bangbang@google.com>

This makes it possible to retroactively link an execution log file to a
particular build.

Closes #24790.

PiperOrigin-RevId: 715017597
Change-Id: Ia8f6a3677a165a9f428b59ab8a19587a357b8803

Commit
https://github.com/bazelbuild/bazel/commit/fd6a9833ba9fe18799193295b82134bc64ab17b3



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

Fixes #24770

Closes #24887.

PiperOrigin-RevId: 714107497
Change-Id: Ib914aa54b2afa2a90fcce2f2263b9c1b2d2c193c

Commit
https://github.com/bazelbuild/bazel/commit/6a141eab3fa5d57eb8b5dadbb6260a120c597fe9



Co-authored-by: Dave Roth <davidroth@google.com>

Fixes #24882

Closes #24883.

PiperOrigin-RevId: 714854122
Change-Id: I5e48e84f88606320223a9969e8367924aeeb13dd

Commit
https://github.com/bazelbuild/bazel/commit/6423b04c1bf95bc0e9ef99667688b3763c3bce4e



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

The jar can be supplied separately as it needs to be passed to the
`-javaagent` JVM arg anyway.

Also update the recommended version for compatibility with Java 21.

Fixes #24782

Closes #24783.

PiperOrigin-RevId: 714057306
Change-Id: Ic8d47562f15344ed16d0af5d3242937d2ee53b22

(cherry picked from commit b59fbeee)

Fixes #24788

This makes it easier for users to discover that a module hasn't been
found because its absence was recorded in the lockfile during a previous
build.

Fixes #24803

Closes #24804.

PiperOrigin-RevId: 713142592
Change-Id: Id541f5710481bd947c09d8dba315d683a1666b1c 
(cherry picked from commit 6061e5ea)

Fixes #24805

Fixes #24730

Closes #24735.

PiperOrigin-RevId: 713606521
Change-Id: If8578fcdfc30dcbfb6af283089614f3364eb30d8

Commit
https://github.com/bazelbuild/bazel/commit/e78bab504940ea2abce749cf8654320cc2fbf96f



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

This protects against an integer overflow which could occur for large
key list size and large thread counts.

Regrettably, it's difficult to write a regression test for this
scenario, as exercising this overflow requires lots of time and heap, so
it would be a performance regression to our test suites.

Fixes https://github.com/bazelbuild/bazel/issues/19445

PiperOrigin-RevId: 595420516
Change-Id: Ic0a475a6a273c50fe9895dd0852fa5b062859cb2

Commit
https://github.com/bazelbuild/bazel/commit/3e373d0abc79e40b3fa46aca4aa268c5ae9b7dc2



Co-authored-by: Googler <cparsons@google.com>

This allows IDEs to query for the direct dependencies of the root module
as well as how they can refer to them from the point of view of the root
module.

Also always emit `name` and `version` so that consumers don't have to
know how to parse module keys.

Work towards #22691

Closes #23787.

PiperOrigin-RevId: 693453084
Change-Id: Ie3fd5e89301d8e83d0eaa686188634923853f01a (cherry picked from
commit 1003d2c3)

Fixes #24678

The warnings tell the user to run `bazel mod tidy`, which is very
confusing.

Fixes #24495

Closes #24729.

PiperOrigin-RevId: 708007222
Change-Id: I60dc889281a776bbf08a7f9537272d7692cce1d8 
(cherry picked from commit 455ddb74)

Fixes #24740

Fixes https://github.com/bazelbuild/bazel/issues/23247

Closes https://github.com/bazelbuild/bazel/issues/24768

PiperOrigin-RevId: 707176116
Change-Id: I71ef3c630f8130467cc6a0c730c1278ae6b0817f
(cherry picked from commit 03eae37f)

…thout the checksum

This PR address the #23932 issue with remote downloader.

Closes #23970.

PiperOrigin-RevId: 686180819
Change-Id: Ia36c5793622bd1ac1fdaa9ef1326ddc385a5a01f

(cherry picked from commit 60638af7

)

Fixes #24837

Co-authored-by: Mislav Mandaric <mislav.mandaric@happening.xyz>

auto does not exist in Bazel 4, 5, 6 or 7. I'm not sure if was there
before but in any of these versions when trying it the following error
appears

ERROR: While parsing option --dynamic_mode=auto: Not a valid dynamic
mode: 'auto' (should be off, default or fully)

Fixes: https://github.com/bazelbuild/bazel/issues/20707

Closes #20705.

PiperOrigin-RevId: 630063050
Change-Id: Ib0b0427268a885d6ffc62c81183b6dd24a6dc517 (cherry picked from
commit a70a28f2)

TEST: bazel build --platforms=//:windows_x86_64
--extra_toolchains=@llvm_mingw_linux_x86_64//:cc-toolchain-linux_x86_64-windows_x86_64
//src/tools/launcher:launcher

Closes #24752.

PiperOrigin-RevId: 711358608
Change-Id: Iedacad9b959427ed5d4598e0ea594cb25b8845c8

Commit
https://github.com/bazelbuild/bazel/commit/a4bb2543bd2e796b472a5c33c1b68b4b9866d977



Co-authored-by: Boleyn Su <boleyn.su@gmail.com>

…rectly to a file

This is a proposed fix for
https://github.com/bazelbuild/bazel/issues/24293

This speeds up a fully warm `bazel query ...` by 23.7%, reducing wall
time from 1m49s to 1m23s

```
$ time bazel query '...' --output=streamed_proto > queryoutput4.streamedproto

real    1m48.768s
user    0m27.410s
sys     0m19.646s

$ time bazel query '...' --output=streamed_proto --output_file=queryoutput5.streamedproto

real    1m22.920s
user    0m0.045s
sys     0m0.016s
```

_‍♂️ Note: when combined with
https://github.com/bazelbuild/bazel/pull/24305, total wall time is 37s,
an overall reduction of 66%._

Closes #24298.

PiperOrigin-RevId: 700583890
Change-Id: Ic13f0611aca60c2ce8641e72a0fcfc330f13c803

Commit
https://github.com/bazelbuild/bazel/commit/791e1f71876daf57b0ac8757eda037148f1470ea



Co-authored-by: Keith Lea <79670223+keithl-stripe@users.noreply.github.com>
Co-authored-by: Yun Peng <pcloudy@google.com>

Work towards #23497
Work towards #24389

Closes #24431.

PiperOrigin-RevId: 698846634
Change-Id: I3fb2d46597b225833a918af9731665bb276322dd

Commit
https://github.com/bazelbuild/bazel/commit/27a5e4593fb661518aaa1bad96ff1fc5257733eb



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
Co-authored-by: Ian (Hee) Cha <heec@google.com>
Co-authored-by: Yun Peng <pcloudy@google.com>

wofstream cannot be constructed from wstring according to the standard
https://en.cppreference.com/w/cpp/io/basic_ofstream/basic_ofstream.

Closes #24703.

PiperOrigin-RevId: 707172911
Change-Id: I973f9560c5b20748e4635cd757f53fff9c8ef0c5

Commit
https://github.com/bazelbuild/bazel/commit/5b35276f57271bf1d81edade231abd667f1d034b



Co-authored-by: Boleyn Su <boleyn.su@gmail.com>
Co-authored-by: Yun Peng <pcloudy@google.com>

Fix for #24530

--experimental_repository_downloader_retries will now retry on
`SocketException` in addition to `ContentLengthMismatchException`

Closes #24608.

PiperOrigin-RevId: 704633572
Change-Id: Idd1fcbb768c9dabed596fe15d8ae9260ef3e895d

Commit
https://github.com/bazelbuild/bazel/commit/459bb5736c5af6fc7a70e1cd9dceb40abb0ad71d



Co-authored-by: Pareesh Madan <pareeshmadan10@gmail.com>

No longer works with python 3.12 or later.

PiperOrigin-RevId: 694480477
Change-Id: Ia662c8fb5511e9c551448730800240ab627463be

Commit
https://github.com/bazelbuild/bazel/commit/5b54c7412cfb251d9ab83e23b37f06504b893331



Co-authored-by: Googler <pcloudy@google.com>

This helps the HTTP downloader better cope with filesystems where unlink
is non-atomic.

Closes #24295.

PiperOrigin-RevId: 697920434
Change-Id: I91b4dbf07a2efdca07c0310e15aac5f4d89c4091

Commit
https://github.com/bazelbuild/bazel/commit/99a27f6d4709516b6210ea4457259f12dd3666ee



Co-authored-by: Simon Thornington <simon.thornington@gmail.com>

[7.5.0] Backport https://github.com/bazelbuild/bazel/commit/9b027c88051797ada7350098ef190191b953014a and https://github.com/bazelbuild/bazel/commit/be2186fbe76ea52b9c146a5f01780a0171384ac8 to fix windows CI failures (#24691)

python: fix bazel py_test testSmoke for Python 3.11+
The test was failing because the `b.py` file couldn't be imported
because, starting with Python 3.11, the `PYTHONSAFEPATH` environment
variable (set by the bootstrap startup) is respected. This setting
inhibits the default Python behavior of adding the main script's
directory to sys.path.

To fix, use `py_library.imports` to explicitly add the necessary
directory to `sys.path`.

Fixes https://github.com/bazelbuild/bazel/issues/20660

Closes https://github.com/bazelbuild/bazel/pull/20738.

PiperOrigin-RevId: 595498775
Change-Id: I0c9521b210fe9e2c40692727fc87d41995e0968a

Commit
https://github.com/bazelbuild/bazel/commit/9b027c88051797ada7350098ef190191b953014a

No public description
PiperOrigin-RevId: 694487395
Change-Id: I3f3e154ebfa932721d917661d61a878477a8e574

Commit
https://github.com/bazelbuild/bazel/commit/be2186fbe76ea52b9c146a5f01780a0171384ac8



---------

Co-authored-by: Richard Levasseur <rlevasseur@google.com>
Co-authored-by: Googler <pcloudy@google.com>

Release Notes:

This PR removes the DownloadManager from the registry factory
implementation. As the registry created by the factory is cached by the
SkyFunction mechanism, the DownloadManager instance was living too long
- it is supposed to be re-created for every command instantiation to
respect changes in command line options, but for the registry, it
ignored those changes.

Instead, the DownloadManager is set directly into the affected
SkyFunctions that require access to it. This way, the per-command
DownloadManager instance is correctly used.

This fixes https://github.com/bazelbuild/bazel/issues/24166

.

Note for reviewers: This is my first time touching code with
SkyFunctions, so I don't really know what I'm doing.

Closes #24212.

PiperOrigin-RevId: 693644409
Change-Id: I7b16684e52673043615290d114f078ab7ab99fcf

Co-authored-by: Cornelius Riemenschneider <cornelius@github.com>

This reverts commit cb1bc28f.

Closes https://github.com/bazelbuild/bazel/issues/24158

PiperOrigin-RevId: 587638256
Change-Id: I4aa6b9c2009323e9c4adc7f6e8b5e335a637ed1c

(cherry picked from commit fb446e63)

Looks like f6687ad4 didn't fully fix
things, based on looking at https://bazel.build/external/module today:

<img width="907" alt="Screenshot 2024-10-15 at 1 13 37 PM"
src="https://github.com/user-attachments/assets/800487d4-0845-418d-8042-bd2c4bad017c">

Closes #23985.

PiperOrigin-RevId: 691071540
Change-Id: Ic474af8308843314aaeaaa85a40dfc487cf7efca

Commit
https://github.com/bazelbuild/bazel/commit/4e4b88fd8385471b783c36f3d9835ba177470fc7



Co-authored-by: Matt Brown <mattbrown@spotify.com>

Since `WorkRequest` encodes strings as UTF-8, Bazel's internal string
encoding of file paths needs to be undone before passing them to the
protobuf builder.

Closes #23924.

PiperOrigin-RevId: 690737819
Change-Id: I3eb341c05e045c75ac004da57e1f46f3587a6810

Commit
https://github.com/bazelbuild/bazel/commit/89f798effcec161c99164f08f58d5565e66c7602



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

`wc -c` has leading spaces that needs to be removed, otherwise
trim_length would become ` 29` for example.

~I'm not very sure how test cases could work but this fails in our
repo.~ I understand it now. We set `IFS=$'\\n\\t'` in our script, which
makes this trick stops working `cut -b ${trim_length}-` (note that there
are no quotes around `${trim_length}`. Although we could fix our `IFS`,
this still seems to be a bug because it is not "portable".

Closes #24076.

PiperOrigin-RevId: 690707015
Change-Id: I728b7462994a6ffdb9b88c3cbea3ec044a8b0134

Commit
https://github.com/bazelbuild/bazel/commit/bf666fb0cb7d74a1005e49cd48bfc790cf46d3a4



Co-authored-by: Honnix <honnix@users.noreply.github.com>

Fixes https://github.com/bazelbuild/bazel/issues/24098

With this change the disk cache garbage collection works correctly:
```
241027 09:06:34.732:I 681 [com.google.devtools.build.lib.remote.disk.DiskCacheGarbageCollectorIdleTask.run] Disk cache garbage collection started
241027 09:07:06.123:I 681 [com.google.devtools.build.lib.remote.disk.DiskCacheGarbageCollectorIdleTask.run] Deleted 190243 of 446229 files, reclaimed 5.4 GiB of 15.4 GiB
```

Closes #24099.

PiperOrigin-RevId: 690652512
Change-Id: Ie8d1fa6b2afb0bd5bd85fdb6835871023a64ad24

Commit
https://github.com/bazelbuild/bazel/commit/374658377f662701f1e92f757090949fdd0da1ab



Co-authored-by: Roman Salvador <rsalvador@salesforce.com>

We want a lower bound, not an upper one.

PiperOrigin-RevId: 690593852
Change-Id: If391e695593c9d445b4968be98d05e6169a06b3a

Fixes #24061

[7.4.1] Revert "[7.4.0] Propagate `linkopts` of header-only libraries to `cc_shared_library`" (#24087)

Reverts bazelbuild/bazel#24017

The change has broken multiple existing builds. Even if it can be fixed,
its usefulness does not justify the potential for more breakages in a
minor release.

PiperOrigin-RevId: 688955616
Change-Id: I408da72cfe409db7feb1978762fc6848f8fe118f (cherry picked from
commit 38833e15)

Release Notes:

createDexMergerActions continues to be exposed to Starlark due to it's
use for SpawnActionTemplate which is not exposed to Starlark. We must
pass a file containing global information to the final dexmerging step
in order to support Java 17 Record desugaring. This change adds an
optional parameter to the Starlark interface to forward the globals file
to the Dex Merger.

PiperOrigin-RevId: 660045021
Change-Id: Ie3b961ff2687f48ca29a94e67180c0e5875ddbe3

Commit
https://github.com/bazelbuild/bazel/commit/2daa0a3d893a3c18021e7c1191d4cacc270dd062



Co-authored-by: Andrew Sinclair <asinclair@google.com>

Fixes #23981

Closes #23982.

PiperOrigin-RevId: 686486627
Change-Id: I5f03b63601a535f8d551c005b00bf040846a324d

Commit
https://github.com/bazelbuild/bazel/commit/b0f1430f0e9b7608b9ecc64b20c3b0fe40ac4a43



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

Fixes #21884
Fixes #23053

Closes #23215.

PiperOrigin-RevId: 686518093
Change-Id: I1a6699b169fe4291ad0dda3be7e74f38c8e37bf1

Commit
https://github.com/bazelbuild/bazel/commit/0fdb36f8a5cf79fda9931b6e3f119bb5f41f0701



Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

When cancelling an asynchronous repository download task, an interrupt
signal is sent to the download thread. This doesn't mean that the
download stops immediately. Avoid restarting a download until the
previous download has actually stopped, so that the new download is able
to clean old data without crashing (on Windows).

Fixes #21773

Closes #23837.

PiperOrigin-RevId: 686175953
Change-Id: I8d75f905b739d38b6cb430d5b5e84fda9a2d14e3

Commit
https://github.com/bazelbuild/bazel/commit/48338d2ff33586a0d053e358da6b94e23fe0e2eb



Co-authored-by: Fredrik Medley <fredrik@meroton.com>