lcmgh

Issue also appeared when using `debian:bookworm-slim`. Can confirm that raising the CPU settings from a fraction of 1 to 2 fixed the issue (Kubernetes). Can confirm that the issue appears...

2 CPUs improved the situation, but when refreshing often same error occurs

The benchmark itself run through fine. What I am getting in the end is: ``` Warning: Failed to comment: HttpError: request to https://my-enterprise.com/api/v3/repos/myorg/my-service/issues//comments failed, reason: tunneling socket could not be...

The log from the previous comment came indeed from a branch triggered build and not from a PR, sorry for that. I have now triggered the action from a pull...

Actually the PR comes from the same repository.

Use case: * There is a library that ships a Builder with default values * Library client microservice wants to use default values and merge in user configured fields On...

> I'd suggest using the `state` value to carry arbitrary payload in addition to a CSRF token (e.g., as a base64url-encoded JSON blob). The OIDC provider will include the `state`...