Fix handling of symbolic/hard links when using `strip_components` (https://github.com/bazelbuild/bazel/pull/30044) ### Description See #29999 which describes a case where using `strip_components` does not properly handle symbolic links. This change consolidates the logic for handling `strip_components` into the `StripPrefixedPath` class which already handled `strip_prefix` logic. With the consolidation, we no longer miss the handling of symbolic and hard links. This code builds on top of the pull request in https://github.com/bazelbuild/bazel/pull/30042 - those commits are included here. It is recommended that you review that pull request before reviewing this pull request (so you don't have to review the same commits twice and to ensure this code is still relevant, since it builds on top of the decisions there). ### Motivation Fixes #29999 - the code that introduced support for `strip_components` didn't handle symbolic links correctly. Fixes #30015 ### Build API Changes No, this is a bug fix. ### Checklist - [X] I have added tests for the new use cases (if any). - [N/A] I have updated the documentation (if applicable). ### Release Notes RELNOTES: Fixes an error when using `strip_components` with archives containing symbolic//hard links. Closes #30044. PiperOrigin-RevId: 953463943 Change-Id: I5da2d3182cc99fb152124c2abb4cc437f6e224d8
{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.
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.
See CONTRIBUTING.md
