Design 47 H: section 10, finding 100
This commit is contained in:
@@ -616,3 +616,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
|
||||
| On the build node the SDK's own integration test of the views reader ("the views reader and two handlers share the module's one durable") failed under the new guard against a second pull loop on one durable (H-A-196), while the same test passed locally at review. The cause, not the guard: the test read the durable's pending-ack count the moment the handlers had spoken, while the reader acknowledges afterwards and the bus takes acknowledgements on its own, so one was still pending on the loaded build node; the test now publishes a mark event and waits for the consumer's acknowledged floor to reach it, fixed in mesh-sdk, in review. The kind: a test reading the bus's acknowledgement count right after a handler speaks; mesh-sdk. Also seen: four release-revision pipelines waited with no steps for over ten minutes behind one running pipeline that could no longer pass, because the pipeline runner (`mesh-delivery-pipeline`) runs one pipeline at a time and ends a pipeline only when its last step ends. Owed: a pipeline that cannot pass ends at once (H-A-163 as written), and the queue's setting is raised once the build nodes allow. | H1 (the SDK's fix); H2 (the queue) |
|
||||
| With the SDK's new guard against a second pull loop (H-A-196), which reads a consumer's cached information at bind, a test fake of a consumer in the indexer (`mesh-delivery-indexer`) that answered no such information panicked, so the indexer's unit step would fail against the new SDK although no indexer code changed; mesh-sdk and the delivery repository's modules. Fixed in H1 by completing the fakes across the delivery repository's modules. Owed: a change of the SDK that adds a call on an interface every module fakes is tried against the modules' suites before its merge (the group's check builds every importer, but runs no importer's suite). | H1 (the fakes); H2 (the check) |
|
||||
| The builder was restarted by hand while Go asks ran in the Go build module's runtime (`mesh-build-go`), whose step list showed none because it does not list the builder's own delivery asks (row 86); the asks survived the restart because the build module runs them, but the "no running step" check before a hand restart is blind to them; the build modules and the runbook. Owed: one tool across the build seats that lists every running ask, whoever asked it. | H2 |
|
||||
| The watchman's entry still pinned no client that its same-repository `buildrun` module requires, because the watchman's go.mod names `buildrun` in a replace directive without a require line, and the reading of the module graph (H-A-201) followed require lines only; six test steps were refused "no pin" (rows 79 and 82); the indexer (`mesh-delivery-indexer`). Settled by H-A-224 (a same-repository module named only by a replace counts as required; its requirements are pinned transitively), in build in the indexer. | settled in H1 once delivered |
|
||||
|
||||
Reference in New Issue
Block a user