| commit | bf666fb0cb7d74a1005e49cd48bfc790cf46d3a4 | [log] [tgz] |
|---|---|---|
| author | Honnix <honnix@users.noreply.github.com> | Mon Oct 28 12:20:31 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 28 12:22:25 2024 -0700 |
| tree | 5b1e0624bb5d95dfe4352dfefef4f4347604f481 | |
| parent | 419fdac42b5f9cc2134462f67c4d0ecbec5bb067 [diff] |
fix: Fix trim_length in runfiles.bash
`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
{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.
Follow our tutorials:
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
