novox/mesh-catalog
18
0
Fork 0
Code Issues Pull Requests 4 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-node/README.md
+2
View File
@@ -41,6 +41,8 @@ state. Whatever the version, the module is healthy and `build_node_health` (the
`steps` with the cause named; the health is then unhealthy with the same text, so the controller raises the machine's
condition. A step runs only after the toolchain directory is installed.
Three read tools answer what the module stored in its own states, without a grant (issue 1562): `build_node_step {id}` is a step's stored value (state, reason, result), `build_node_steps {limit}` this machine's latest steps without their results, and `build_node_toolchains` every `<node>.<language>` key of `toolchains`.
## Tools
`build_node_status` and `build_node_health` answer in their call. The step tools run behind the guard and the