Interesting approach by Russ for finding bugs by diff code coverage profiles between faing and success exectuon:
https://research.swtch.com/diffcover
https://research.swtch.com/diffcover
Classics https://status.redhat.com/
> Quay.io has been moved to read-only mode while we work to implement a fix. During this time Pulls will continue to work, however, Pushes will be disabled until a fix is implemented. There is currently no timeline for Push restoration.
> The issue has been identified. A primary key in the database has reached maximum value. We are currently working on validating a fix.
> Quay.io has been moved to read-only mode while we work to implement a fix. During this time Pulls will continue to work, however, Pushes will be disabled until a fix is implemented. There is currently no timeline for Push restoration.
> The issue has been identified. A primary key in the database has reached maximum value. We are currently working on validating a fix.
Redhat
Red Hat Status
Welcome to Red Hat's home for real-time and historical data on system performance.
Nice satire article https://www.justfuckingcode.com/ π Kinda true in many directions π
Hey k8s/containers users!
Go 1.25 not yet released but will be container aware of GOMAXPROCS https://tip.golang.org/doc/go1.25#container-aware-gomaxprocs
Go 1.25 not yet released but will be container aware of GOMAXPROCS https://tip.golang.org/doc/go1.25#container-aware-gomaxprocs
tip.golang.org
Go 1.25 Release Notes - The Go Programming Language