20d59ff4f02a4c735a13703baea20549054de652
grants-for read two whole catalog revisions page by page on every call (about 1.4 MB each) and answered in 3.4 to 5.0 s, so the pipeline runner's 5 s read bound cut it and every widening touching the vault said "could not run". A revision never changes, so the part now keeps each revision it read whole, by branch, kind, group, heads and number, the newest four per branch for the process's life (as the runner keeps its revisionCache); once a first page names a kept revision the pages after it are not read. The branch's newest is read on by the number its first page names, and a revision whose pages name another is not kept. Quick fix (not chosen): raise the runner's widens read bound, a catalog merge that hides the cost. Thorough fix (chosen): the cache here. The compose of every account twice is kept whole: narrowing it to the candidate's modules would stop a refused principal elsewhere from failing grants-for, which is not obviously safe. Builds: design 47 G §441, §401; H §774
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.
Description
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
37 MiB
Languages
Go
99.2%
JavaScript
0.8%