Point R325 at #150's head after its rebase and review
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go)
mesh/delivery-group group fix/assign-says-why-a-module-is-not-there checking: 1 of 2 member(s) ready
mesh/delivery superseded: a newer head of the same pull request

The fix moved to dd78357 on main 056414b; proved again there.
This commit is contained in:
jochen
2026-10-08 16:22:30 +02:00
parent c02a8ec4c8
commit 5c128c1c18
+3 -3
View File
@@ -213,9 +213,9 @@ var Register = []Replay{
// An assignment answered as unknown while its module's build ran (2026-10-08): the merge adding `sensors`
// asked for its build (issue 300), and `assign g14 sensors` a minute later said "no module of that name",
// which read as a module nobody registered. A test in the controller, written with only what it had
// before the fix, laid over the commit before. The fix is still on its branch: proved against the main it
// branched from.
{ID: "R325", Issue: 325, Kind: InRepository, Repository: "mesh-controller", Fix: "b93dea8", Before: "a759ac6",
// before the fix, laid over the commit before. The fix is still on its branch: Fix is its pull request's
// head, proved against the main it is rebased on.
{ID: "R325", Issue: 325, Kind: InRepository, Repository: "mesh-controller", Fix: "dd78357", Before: "056414b",
What: "a minute after the merge that added sensors asked for its build, assign g14 sensors answered no " +
"module of that name, and the same call worked minutes later",
Asserts: "an assignment made while its module's build runs says the build, is kept, and is made when the " +