Tristan Keen

While this PR has been tested and Works-For-Me (tm), https://github.com/actions/python-versions/pull/275 sounds like it would be a better fix if it works as advertised, gets released & the pythons rebuilt...

FYI a similar bug we still have with 0.12.0 that others might be experiencing but isn't quite the same (our stuck runners stay forever in `Running` state with failures in...

@rentziass is this API side fix a concern for people running ARC with Github Enterprise Server? E.g. does the latest GHE 3.17.1 release contain anything that would help this issue...

@yoannchaudet has this fix made it to any published GHES version yet ~~(I can't see anything like it in the release notes)~~? FWIW we're seeing it in v3.10.7 that came...

It's at least still present on v1.7.0 (what we are testing currently when I came across a similar problem).

Surprised you're getting a 406 error with v1.7.0 - I'm seeing a 500 error with the same error in the engine's logs as shown in #4455

@vflaux might be worth [sorting your DCO issues](https://github.com/containerd/project/blob/main/CONTRIBUTING.md#sign-your-work) while waiting for review, but I don't know why this PR is rated "large" given it's mostly tests for a pretty small...

We have a number of custom systems feeding events (AWS, Cloudflare, GitHub, etc.) which translate the events into OnCall alerts that expect to group the "OK" message the same as...

FWIW adding the readinessCheck (& switching to strategy Recreate) didn't actually fix the kube-prometheus-stack `TargetDown` alert - the `endpoints` were still there (in our EKS 1.22 cluster) and so used...