Design 47 H: section 10, finding 96
This commit is contained in:
@@ -612,3 +612,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
|
||||
| The joined pipeline runner (`mesh-delivery-pipeline`) crashed at every start on the control-node ("concurrent map writes" in its per-mover step store: the store's shared maps were written under each pipeline's lock only, while the start placed several branches' waiting pipelines at once) and was rolled back within a minute. Before dying it had split two kept pipelines into per-mover keys, and the old runner then placed one running pipeline's steps again from the emptied record, losing that record's history; no hand repair, as the new runner composes from the keys; the pipeline runner. Settled in H1 by a mutex over the store's maps and a run of the race detector over the runner's start path with kept pipelines. Owed: every module's unit and integration suites run under the race detector in the check, and a tool that lists the runner's state keys (a whole list exceeds the bus; no key listing exists). | H1 (the fix); H2 (the check and the tool) |
|
||||
| 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 |
|
||||
|
||||
Reference in New Issue
Block a user