7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	83ce19b9c0	Say a registry came back only when the call worked, and retry from toRetry's set (issue 457 review) ... The streaming blob PUT is left unwaited, with why, since its body cannot be read twice and the POST before it already waited.	2026-10-11 11:05:30 +02:00
jochen	c5663aa18b	Let platform manifests go only on a confirmed collect, and copy again what a sweep took ... An unrecorded index or a copy in progress can name a platform the records do not see, so only a person's collect, after its dry run, takes an index's platforms, and only once every kept index of each repository it touches was read. A copy missing a platform is copied again, and a copy a build holds again is no longer recorded as collected (review of #144).	2026-10-08 15:47:42 +02:00
jochen	9907df6530	Record the bases a build copies, keep them by the builds that stood on them, and copy each image once ... A copied base was named only in what a build stood on, and nowhere when the build failed, so the store's sweep could never let one go (hq issue 321). One repository per upstream image stops each module asking the public registry for the same image again, and letting an index go now takes its own platform manifests, which otherwise kept every byte. A person can record the copies no record names through the new mirrors verb (hq ADR 0257). The forge test fix is the same commit as on feat/plain-notifications: main fails without it.	2026-10-08 15:47:42 +02:00
jschoubben	338d033632	A manifest HEAD says what it accepts, or the registry answers 404 ... The check that skips copying a base the mesh already holds asked with no Accept header, and a registry answers a manifest only in a media type the caller named: the same digest answered 200 with the manifest types and 404 without them. So the builder concluded it held nothing, copied every vendor base again, and exhausted the public hub's pull limit a second time today. The test could not have caught it, because the fake registry answered a manifest HEAD regardless of Accept — more permissive than the thing it stands in for. It is now as strict as a real registry, and fails without the fix.	2026-09-28 13:02:08 +02:00
jschoubben	3756bb3460	A base the registry already holds is not pulled from upstream again ... A base is named by digest, and a digest the mesh's registry holds under the module's repository is the same bytes whatever upstream would say. Asked on every build, the public hub's anonymous pull limit was reached on the first merge that rebuilt a whole catalogue, and every module whose base lives there failed on a copy it did not need.	2026-09-28 04:48:32 +02:00
jschoubben	9f3790dcda	Review: one local name is still a local name; a local name is unique; recovery knows it; recipes read as instructions; a tag before a digest; ask fails at once when nothing serves ... A secrets object with one local name delivered no file. Two requirements could share a local name. secret recover and the export could not tell two locals apart. The recipe check missed continued lines and read heredoc bodies as bases. repo:tag@digest kept the tag in the repository. ask now publishes mandatory, so a tool nothing serves is said at once rather than after the wait.	2026-09-21 21:03:22 +02:00
jschoubben	412599de9a	An upstream image is copied between registries, never through a machine's image store ... A published image is an index over several architectures; pulled, the runtime's store keeps the index and refuses to push one platform out of it. The builder now reads the index and every manifest it names over the registry API, with the anonymous bearer token the public hub hands out, moves each blob by digest into the mesh's registry, puts the manifests and then the index under the module's repository, and pins the index. Genesis, with no registry to copy into, keeps the pull (novox/hq 04-ISSUES/046, ADR 0096).	2026-09-21 20:42:30 +02:00