Tiago Quelhas

@bazaglia I'd like to look into this, but reproducing it seems to be quite involved. Do you have a repro that does not require setting up a GitHub action? I...

The difficult part for me isn't setting up the GitHub repository, it's configuring the GCP workload identity provider: the google.com GCP org policy forbids me from using `https://token.actions.githubusercontent.com` as the...

I was able to repro this today. It looks like there's a bug in the `google-auth-library-oauth2-http` library. I've sent https://github.com/googleapis/google-auth-library-java/pull/984 to fix it.

I'm no longer convinced there's a bug in google-auth-library-oauth2-http. The test case I added in googleapis/google-auth-library-java#984 passes even without the fix (as the maintainer pointed out). I'm fairly sure PR...

How exactly are you building and running Bazel? In particular, how does the built Bazel make it into the GitHub action execution environment?

Ok, so here's how I verified that it works for me: - I checked out the https://github.com/tjgq/bazel/tree/auth branch and built a Bazel with `bazel build //src:bazel` at commit a416cea. -...

It will definitely be included in 6.0, but I'm reluctant about backporting it to 5.3.1. There's a lot of complexity in the interaction between Bazel and the OAuth2 support libraries,...

`ctx.actions.symlink` actually does two completely different things, depending on whether the `output` argument is a `ctx.actions.declare_symlink` or a `ctx.actions.declare_file`. The first case indeed creates a symlink. The second case is...

But `--experimental_allow_unresolved_symlinks` only applies to `ctx.action.symlink` with a `ctx.actions.declare_symlink` output argument, right? The provided repro is specifically about a `ctx.actions.declare_file` argument, which I believe is working as intended.

> @tjgq : My understanding is that I use the experimental feature `ctx.actions.declare_symlink` if I want to allow _dangling_ symlinks that are created by an action. In my case I...