Design 47 H: section 10, finding 97
This commit is contained in:
@@ -613,3 +613,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
|
||||
| The indexer (`mesh-delivery-indexer`) refused its own take-in-again tool's ask ("a takeins value naming no hand act the indexer serves"): the decoder of a take-in ask kept a hand-written list of hand-act fields that the new field was not added to, and no test sent a tool's value through the decoder; the indexer. Settled in H1 by deriving the check from the ask's fields, and by a table test that decodes every tool's value. Owed: the same table test for every module whose tools write asks its daemon decodes. | H1 (the fix); H2 (the kind across modules) |
|
||||
| The seat mesh-catalog's revision verb answered from the tools bundle's view of the trunk in memory, which ran one or more revisions behind the kept revisions once releases kept several in a row, so the pipeline runner waited minutes for a revision the indexer had kept (four minutes for revision 52) and the builder's picture failed a pipeline's first builds past its bound (rows 68 and 84); the indexer (`mesh-delivery-indexer`) and the builder. Settled by H-A-222 (the verb answers the newest kept revision read from the store at the ask; the builder's picture holds an ask that names a kept revision number, read by number), in build. | settled in H1 once delivered |
|
||||
| A release re-pinned a mover of a running pipeline of 120 movers (the tool runner, pinned to the SDK's new version) while that pipeline still built it at the old fingerprint; the build failed and, as a pipeline passes or fails whole, took every other mover with it, because the runner moved only movers of waiting pipelines; the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-223 (a moved mover leaves a running pipeline too: its steps end superseded, its asks are cancelled, the end judgement counts it as left; a pipeline whose every mover left ends superseded), in build in the runner. Also seen in the same pipeline: two builds done "but no version is reserved", because the builder's picture lagged the revision that named their fingerprints (row 95's cause). | settled in H1 once delivered |
|
||||
| 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; cause under study (a second bind the reader makes, or the test's own); the fix keeps one pull loop per durable per process, with the handlers fanning out from it, in build; 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) |
|
||||
|
||||
Reference in New Issue
Block a user