novox/mesh-catalog
18
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request 'Let the build modules answer their own step results and toolchains, so a fetch's workspace and a build's digest can be read (issue 1562, build-module half)' (#410) from fix/1562-read-steps into main

Browse Source
This commit was merged in pull request #410.
This commit is contained in:
mesh-tools
2026-10-21 10:26:13 +00:00
parent 940594b074 c33b83dce7
commit 710cfbd622
16 changed files with 734 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/mesh-build-go/README.md
+2
View File
@@ -29,6 +29,8 @@ cause named, and the health is then unhealthy with the same text, so the control
`build_go_digest`, `build_go_build`) are added by their own issues to `StepTools` and run behind the guard: a long
step answers at once with its id and ends on `<node>.<id>` of `steps` (ADR 0469 §2); the digest answers in its call.
Three read tools answer what the module stored in its own states, without the guard and without a grant (issue 1562): `build_go_step {id}` is a step's stored value (state, reason, result, such as a fetch's workspace id), `build_go_steps {limit}` this machine's latest steps without their results, and `build_go_toolchains` every `<node>.<language>` key of `toolchains`.
## Fetch
`build_go_fetch {repository, commit, ref?}` fetches the commit over SSH as the module's account (`mesh-forge` is the