Luiz Carvalho

I think this might contain all the needed data:https://github.com/hexorx/countries/blob/master/lib/cache/translations.yaml

@anderseknert, no worries! FWIW, it's possible to reproduce the issue with just GitHub actions as mentioned in the description. It's definitely not as easy to debug as a local system,...

Still failing on opa v0.40.0 with the same error.

@oglok, the containerized version with podman. Thanks!

@jeremycline, ah that's clever because I can do that on my consumer directly (I think) without having to mess with fedmsg/moksha. Thanks, I'll look into that.

> The way we've handled this in fedora-messaging is to register signal handlers. I'd recommend that approach. Handle the signal by setting a "stop" flag, and if that flag is...

[TEP-84](https://github.com/tektoncd/community/blob/main/teps/0084-endtoend-provenance-collection.md) is related to signing of PipelineRuns.

One possible explanation for this behavior is that while the controller is reconciling a given version (A) of the TaskRun, a new version (B) of the TaskRun is created and...

There's another possibility here. I found an article that states a controller should stick to [One Custom Resource Modification at a Time](https://cloud.redhat.com/blog/7-best-practices-for-writing-kubernetes-operators-an-sre-perspective). Digging through the code, it looks like in...

In the case of a non-successful TaskRun, its attestation will always in include a `null` value for the subject. This is because a non-successful TaskRun produces no results, thus Chains...