mesh-delivery

novox/mesh-delivery

Fork 0

Files

T

History

jschoubben 3e7f852472

mesh/delivery held for a person: merged without a passing check: only a person decides what follows

Details

mesh/check failed: integration: mesh-delivery-indexer/cmd/mesh-delivery-indexer.TestIndexerCountsOnlyTheAssignedBuildNodesToolchains: within 5 s of n2…

Count a build node's toolchain report only once written since its assignment, and keep a computed fingerprint while builders disagree (issue 1940)

On 2026-10-25 20:56 assigning mesh-build-node to ace again brought ace's report of 2026-10-23 (v26.12.0) back into the
agreement before the module ran there; the indexer blanked every module's fingerprint to "builders disagree" and the
controller's take-in refused modules already computed and built.

- The toolchain gate (indexer, builder, checker; still one file in three) leaves a report out, said once, until its node
  writes it since its current assignment: the assignment's own time, or the revision that opened it.
- The indexer keeps a module's held fingerprint while a language has no agreed toolchain, when its kept inputs with the
  toolchains it was computed with give it again; only a new fingerprint (a merge, a base, an agreed toolchain moved)
  needs the agreement.

2026-10-25 21:03:16 +01:00

cmd

Count a build node's toolchain report only once written since its assignment, and keep a computed fingerprint while builders disagree (issue 1940)

2026-10-25 21:03:16 +01:00

internal/check

mesh-delivery-checker: a package sent as its FAIL line alone is still worded, and the words keep their bound exactly (issue 1901, review round 1)

2026-10-25 15:58:09 +01:00

go.mod

Read a level's digest from mesh-sdk's list form, so kept verdicts hold for a check whose end names a package like token (issue 1930)

2026-10-23 23:37:49 +02:00

go.sum

Read a level's digest from mesh-sdk's list form, so kept verdicts hold for a check whose end names a package like token (issue 1930)