Timotheus Bachinger

I have currently a work around in place by using a fork in our build process in case any body needs a quick solution: https://github.com/Checkmk/checkmk/commit/36ae1e1230cacd53a508a7c2eed6d9f2fdf8f6f5 and https://github.com/Checkmk/netapp-ontap-cmk/commit/e38ce4ce357ad2ea8f47260c269757f8805bdbce

Dear Checkmk Contributor! Unfortunately, we had to re-write our git-repo history, rendering your PR auto-closed. We will therefore rebase your PR onto the current master and reopen it again. Sorry...

Dear Contributor. Unfortunately, we learned that re-opening a PR which was force-rebased, is not possible (see https://github.com/isaacs/github/issues/361). Therefore we kindly ask you to create a new PR for your change....

I don't completely understand. using `create_venv` from `rules_uv` correctly populates the `bin` folder, this is our current workaround, see https://github.com/Checkmk/checkmk/blob/042eb9193a092a22592d56cd3c34f27de8b17eb7/packages/cmk-agent-based/run#L119C19-L119C26 are you planing to switch also to `rules_uv`? or would...

Hi drake-guys, we're also heavily facing exactly the same issue in combination with bazel mod + github: ``` Error in download: java.io.IOException: Error downloading [https://github.com/bufbuild/buf/releases/download/v1.27.0/buf-Linux-x86_64] to /home/jenkins/.cache/bazel/_bazel_jenkins/511ee6f5c2c78f955f5cedd45e175c7b/external/rules_buf~~ext~rules_buf_toolchains/buf: GET returned 618...

Hey @jwnimmer-tri ! > Do you have your own issue posted anywhere else, where we could subscribe to follow in case you solve it? not yet - it is astonishingly...

Dear Checkmk Contributor! Unfortunately, we had to re-write our git-repo history, rendering your PR auto-closed. We will therefore rebase your PR onto the current master and reopen it again. Sorry...

Dear Contributor. Unfortunately, we learned that re-opening a PR which was force-rebased, is not possible (see https://github.com/isaacs/github/issues/361). Therefore we kindly ask you to create a new PR for your change....

Dear Checkmk Contributor! Unfortunately, we had to re-write our git-repo history, rendering your PR auto-closed. We will therefore rebase your PR onto the current master and reopen it again. Sorry...

Dear Contributor. Unfortunately, we learned that re-opening a PR which was force-rebased, is not possible (see https://github.com/isaacs/github/issues/361). Therefore we kindly ask you to create a new PR for your change....