Design 47 H: section 10, findings of H1's live run (16:40 to 18:40)
This commit is contained in:
@@ -501,3 +501,53 @@ milestone named, written into its part before that milestone's prepare.
|
||||
| mesh-delivery-sdk and mesh-delivery-contracts publish as packages of their own. | H2 |
|
||||
| The hand pack's `build-seats` phase carries the label of the build node only; every machine with a build runtime needs it. | H1, the runbook |
|
||||
| The claude-code node side wrote a lease over a login the manager had not adopted (H-A-138); its fix is a small fix beside H1. | fixed in H1 |
|
||||
|
||||
Added by the lead at 18:40 CET, from the run of 16:40 to 18:40: the first delivery by pipeline landed (a module on the
|
||||
desktop, with hand restarts), and these were met on the way. A row a lead answer settled says so; the rest are open.
|
||||
|
||||
| finding | milestone |
|
||||
|---|---|
|
||||
| Validate's base was read as the source number minus one, which names nothing where a take-in moved nothing (the seed, a merge with no mover); the indexer (`mesh-delivery-indexer`) and the assigner's validate. Settled by H-A-151 and H-A-154 (the catalog revision's field `base`), which settle the first-revision row above too. | settled in H1 |
|
||||
| Compositions on the control-node failed on stale assignments (modules assigned that no watched branch lists); the assigner (`mesh-delivery-assigner`). Settled by H-A-152 and H-A-153 (the run value's field `unlisted`, in the seat mesh-wants), proven at main.24. | settled in H1 |
|
||||
| A build ask reached the builder before its picture held the pipeline's revision, so it built with no version reserved (main.8, main.21, the first proof); the builder. Settled by H-A-155, H-A-156 (`revision-wait-minutes`) and H-A-162 (a run's ask names no source). | settled in H1 |
|
||||
| 64 of 82 Go modules carried no package edge, because the indexer read mesh packages from go.sum, which names none at the zero version; the indexer. Settled by H-A-157 (edges from go.mod). | settled in H1 |
|
||||
| The tool runner (`node-tools`) stopped every subscription on each membership and repair and dropped calls in the gap; the tool runner. Settled by H-A-158 and H-A-160 (make before break). | settled in H1 |
|
||||
| The builder still numbered every trunk build in a `versions` state of its own and folded a reserved version into an older entry, so builds pinned an old package; the builder. Settled by H-A-159 (the reservation is the one numbering), which also makes a tool to drop or rewrite a versions entry moot. | settled in H1 |
|
||||
| Packages were pinned by a commit (a pseudo-version of an old tree), so builds ran against pre-H1 packages (main.15, main.20, main.22, main.24); the indexer and the builder. Settled by H-A-161, H-A-165 (`package-wait-minutes`, a re-pin on version-released), H-A-167 and H-A-172 (pins in every form's fingerprint). | settled in H1 |
|
||||
| A pipeline whose mover had no registration never ended (main.20, main.22), and no tool ended a pipeline by hand; the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-163, H-A-171 and H-A-164 (the seat verb `end-again` on mesh-pipeline-runner, the tool `runner_end_again`). | settled in H1 |
|
||||
| The SDK's view reader heard an event only on `<subject>.>`, so the seat mesh-catalog's registration-changed on its bare subject reached no handler; mesh-sdk. Settled by H-A-166 and H-A-169 (the finding `event-unhandled`). | settled in H1 |
|
||||
| The SDK's finding write for an unhandled event waits up to 3 s on the bus inside the event loop, per event, so a missing stream or a slow bus stalls the module: write it outside the loop, or once per change of the count; mesh-sdk. | H2 |
|
||||
| The indexer dropped a passed pipeline's revision once the pipeline ended, so the want named an entry no longer kept and was held "entry-missing" (main.23, main.25); the indexer. Settled by H-A-168, H-A-170, H-A-173 and H-A-174 (release pins). | settled in H1 |
|
||||
| A tier-late pipeline's release records are freed only by that module's next pipeline that ends running, so a module with no later pipeline keeps its revisions pinned; the indexer. | H2 |
|
||||
| The indexer's `publishedAsBuilt` may read a package's imports at the wrong commit when the pin is not the newest of its series; the indexer. | H2 |
|
||||
| A failed re-pin leaves a pending key behind; the indexer. | H2 |
|
||||
| A build module's toolchain edge into the movers it is built from made a cycle the runner never broke, so pipelines held their turn with no step for an hour (main.26, main.28, main.30); the pipeline runner. Settled by H-A-175 and H-A-176 (the pipeline ends failed with why `cycle`). | settled in H1 |
|
||||
| Integration tests pass alone and fail on the build node under load (the bridge, the grants part, the indexer, the assigner's setup at 38 s against 30 s, the tool runner's level at 72 s against 60 s), because a build node runs levels side by side; fixed per test for the indexer and the tool runner only; the Go build module (`mesh-build-go`) and each module's tests. | H2 |
|
||||
| The Go build module runs builds at idle CPU priority, so a fixed bound in a test or a step can be outlasted by load alone; the Go build module. | H2 |
|
||||
| The build node counts untagged tests into a module's integration count (156 against the budget of 50 for the pipeline runner); the Go build module. | H2 |
|
||||
| Modules over the test budget: the node-engine (`mesh-host`) with 1716 unit tests against 500, the indexer with 538 integration tests and the assigner with 64, against 50; each shrinks with every change to its tests. | H2 |
|
||||
| The Go build module reads failed on the control-node and on the laptop, and a third build node is paused, so one build node (the desktop) builds for the whole mesh. | H2 |
|
||||
| The builder still starts delivery builds from the take-in path, flooding the one build node, where H §756 says a build is entered only by the runner's build step; the builder. | H2 |
|
||||
| A newer pipeline withdraws an older pipeline's build of the same module, and the older pipeline then fails instead of that mover leaving it (main.27, withdrawn by main.30); the pipeline runner and the builder. | H2 |
|
||||
| The step outputs store keeps 0 bytes, so the words of a failed test are lost and only the verdict remains; the pipeline runner. | H2 |
|
||||
| The pipeline runner's `show` answers 150 KB with no filter, too large for a session to read; it needs a filter (a mover, a step, a state); the pipeline runner. | H2 |
|
||||
| A run on request cannot place steps for a module that is not a mover; the pipeline runner. | H2 |
|
||||
| `runner_start` refuses a head whose pipeline exists (H-A-52), so a package module is built again only by a new merge; the pipeline runner. | H2 |
|
||||
| A required step that could not run has no hand twin: accepting it and running it again are both refused; the pipeline runner. | H2 |
|
||||
| No tool places a pipeline's waiting movers again; only the runner's start does; the pipeline runner. | H2 |
|
||||
| No tool shows the pins a build ask carried; the builder. | H2 |
|
||||
| `builder_build_again` refuses a key that is done; the builder. | H2 |
|
||||
| The seed registered not every package module (mesh-delivery-contracts, mesh-delivery-sdk) and made no mover of them, so they were registered by hand and nothing was published at H1's heads (H §758); the seed of the seat mesh-catalog. | H2 |
|
||||
| A want is written only from a pipeline that passed whole (H §750, §751), so a dependent folded in (H §745) that fails blocks a fix of the module it depends on; the assigner. A design question: all or nothing, or per mover. | H2 |
|
||||
| Packages in one repository carry no kind-1 edge between them (the sibling rule, H-A-136); a design question whether they should; the indexer. | H2 |
|
||||
| A module (`feh:tools`) carries a required integration step with no integration test to run ("a step with nothing to run"); the seed's steps in the seat mesh-catalog. | H2 |
|
||||
| The gate (`mesh-delivery-gate`) says old sources again on a restart. | H2 |
|
||||
| A held take-in does not try again after a passing failure of the forge; the indexer. | H2 |
|
||||
| The node-engine's early-pass words "reaches no artifact store" read as a fault while placements are not read yet; the node-engine. | H2 |
|
||||
| The node-engine's resolve-again period is fixed in code, not a setting (P11); the node-engine. | H2 |
|
||||
| A fetch made inside the node-engine's turn tells the composer nothing; the node-engine. | H2 |
|
||||
| The node-engine's node-agent wiring has no test; the node-engine. | H2 |
|
||||
| A bundle reload of the tool runner still unloads before it serves, so calls in the gap meet no responders (said, not silent), and the mesh MCP server's package takes 28 s to load; the tool runner. | H2 |
|
||||
| The seat node-files has no verb that reads a file's sha256, and its `copy` refuses another node (issue 903), so hand packs were copied by the lead's shell; node-files. | H2 |
|
||||
| The builder's unit written by hand on the desktop carries none of the manifest's setting variables, so its settings are the defaults; the builder's hand pack. | H1, the runbook |
|
||||
| The clean proofs of the runbook's step 7 are still owed: the first proof failed on the version race (settled by H-A-155), the second ran for the publish of the SDK packages; the freeze is not lifted (step 8). | H1 |
|
||||
|
||||
Reference in New Issue
Block a user