[9.3.0] Lock in the first observed value of a recorded input (#31091) (#31143)

### Description
`RepoRecordedInput.File.fileValueToMarkerValue` re-hashes the file from
disk whenever the cached `FileValue` has no fast digest, i.e., pretty
much in all cases for Bazel. As a result, a repo rule or module
extension that reads a file, modifies it (e.g. via `ctx.execute`) and
then reads it again observes two different digests for the same input.
Since 41ccfefb88e, `recordInputWithValue` turned this into an
`IllegalStateException` that crashed the fetch.

Instead, keep the value observed first and emit a single warning per
input whose value changed during the evaluation. The first value no
longer matches the on-disk state after the fetch, so the repo or
extension is re-evaluated exactly once more on the next invocation and
is stable from then on if it leaves the file unchanged.

### Motivation
Fixes #29114

### Build API Changes

No

### Checklist

- [x] I have added tests for the new use cases (if any).
- [ ] I have updated the documentation (if applicable).

### Release Notes

RELNOTES: None

Closes #31091


COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31091
from fmeum:fix-29114-locked-in-recorded-inputs
f2fc00e34169108e08573e226ede587a625fa56e
PiperOrigin-RevId: 981856410
Change-Id: I3643f71ba2e492bdc16d3a724f0cb9cb806972a0

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

Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
4 files changed
tree: 7ef204a742de56ef3aa1cb2a49b19601dce827b8
  1. .bazelci/
  2. .github/
  3. docs/
  4. examples/
  5. scripts/
  6. site/
  7. src/
  8. third_party/
  9. tools/
  10. .bazelrc
  11. .bazelversion
  12. .gitattributes
  13. .gitignore
  14. AUTHORS
  15. bazel_downloader.cfg
  16. BUILD
  17. CHANGELOG.md
  18. CODE_OF_CONDUCT.md
  19. CODEOWNERS
  20. combine_distfiles.py
  21. combine_distfiles_to_tar.sh
  22. compile.sh
  23. CONTRIBUTING.md
  24. CONTRIBUTORS
  25. distdir.bzl
  26. extensions.bzl
  27. LICENSE
  28. maven_install.json
  29. MODULE.bazel
  30. MODULE.bazel.lock
  31. README.md
  32. repositories.bzl
  33. requirements.txt
  34. SECURITY.md
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Reporting a Vulnerability

To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.

Contributing to Bazel

See CONTRIBUTING.md

Build status