Skip to content

Allow specifying where stdout should get written#526

Merged
fweikert merged 1 commit intobazelbuild:masterfrom
illicitonion:allow-custom-stdout
Apr 18, 2024
Merged

Allow specifying where stdout should get written#526
fweikert merged 1 commit intobazelbuild:masterfrom
illicitonion:allow-custom-stdout

Conversation

@illicitonion
Copy link
Copy Markdown
Contributor

This can be useful when invoking bazelisk programatically.

This can be useful when invoking bazelisk programatically.
@illicitonion
Copy link
Copy Markdown
Contributor Author

@fweikert Any chance of a quick look at this tiny (but slightly ugly!) PR? Thanks!

@fweikert fweikert merged commit 24651ab into bazelbuild:master Apr 18, 2024
@illicitonion illicitonion deleted the allow-custom-stdout branch April 18, 2024 14:51
dodial20

This comment was marked as spam.

ti-chi-bot bot referenced this pull request in PingCAP-QE/artifacts Jul 3, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [bazelbuild/bazelisk](https://togithub.com/bazelbuild/bazelisk) |
minor | `v1.19.0` -> `v1.20.0` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>bazelbuild/bazelisk (bazelbuild/bazelisk)</summary>

###
[`v1.20.0`](https://togithub.com/bazelbuild/bazelisk/releases/tag/v1.20.0)

[Compare
Source](https://togithub.com/bazelbuild/bazelisk/compare/v1.19.0...v1.20.0)

Bazelisk v1.20.0 comes with several significant changes:

### New Features

- The Go version now supports `BAZELISK_NOJDK`
([https://github.com/bazelbuild/bazelisk/pull/531](https://togithub.com/bazelbuild/bazelisk/pull/531))

### Bug Fixes & Improvements

- It's now easier to use Bazelisk programmatically
([https://github.com/bazelbuild/bazelisk/pull/500](https://togithub.com/bazelbuild/bazelisk/pull/500),
[https://github.com/bazelbuild/bazelisk/pull/526](https://togithub.com/bazelbuild/bazelisk/pull/526))
- Bazelisk will retry more connection errors
([https://github.com/bazelbuild/bazelisk/pull/529](https://togithub.com/bazelbuild/bazelisk/pull/529),
[https://github.com/bazelbuild/bazelisk/pull/530](https://togithub.com/bazelbuild/bazelisk/pull/530))
- A display bug in the download progress bar has been fixed
([https://github.com/bazelbuild/bazelisk/pull/539](https://togithub.com/bazelbuild/bazelisk/pull/539))

We’d like to thank our amazing contributors
[@&#8203;afq984](https://togithub.com/afq984),
[@&#8203;comius](https://togithub.com/comius),
[@&#8203;francine-blanc](https://togithub.com/francine-blanc),
[@&#8203;illicitonion](https://togithub.com/illicitonion),
[@&#8203;jwnimmer-tri](https://togithub.com/jwnimmer-tri),
[@&#8203;LINKIWI](https://togithub.com/LINKIWI),
[@&#8203;mmorel-35](https://togithub.com/mmorel-35) and
[@&#8203;sf-jbazuzi](https://togithub.com/sf-jbazuzi)!

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/PingCAP-QE/artifacts).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zNjMuNSIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJoZWxwIHdhbnRlZCJdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants