mesh-lab/replays/go.mod at 14246bcf0125ecd67271aa9b642b7c4b30d7137c - mesh-lab - Gitea: Git with a cup of tea

Files

T

jochen 70f62ee17b Replay the core incidents, and prove each fails before its fix and passes on it (hq to-be 45 §9)

Phase 5 is done when the replays of 236, 262, 263 and 266 fail on the commit before their fix and
pass after. The register names every replay with its issue and fix; the bus replay (266) runs a
consumer filtered like the controller's against a bus of a given release, the resolver replay (262)
renders the catalogue's machine list and asks every machine's name by getaddrinfo under musl and
glibc, and the prover runs each at both commits: all five (236, 262, 263, 266, 273) proved.

2026-10-06 21:01:39 +02:00

14 lines

329 B

AMPL

Raw Blame History

 module github.com/novox/mesh-lab/replays
 go 1.26.0
 require github.com/nats-io/nats.go v1.54.0
 require (
 	github.com/klauspost/compress v1.20.0 // indirect
 	github.com/nats-io/nkeys v0.4.16 // indirect
 	github.com/nats-io/nuid v1.0.1 // indirect
 	golang.org/x/crypto v0.57.0 // indirect
 	golang.org/x/sys v0.48.0 // indirect
 )