Design 47 H: H-A-335, the held-module rule covers every runtime's slice
This commit is contained in:
@@ -2021,3 +2021,9 @@ Where two preparers disagreed, the chosen one is named.
|
||||
(3) the error kind "away" widening ADR 0664 §1 and ADR 0668 §1 is a progressive insight on ADR 0668 proposed by the
|
||||
record writer; (4) the items of section 10 rows 41 to 102 marked H2 go into a second part, H2b, written next; design
|
||||
47's main file's size is a separate reshaping run. act-on-the-intent, P7.
|
||||
- **H-A-335 (the held-module rule covers every runtime's slice, 21:58)** With the fixed node-engine on the home server the
|
||||
tool runner stopped restarting (none in five minutes after the hold's release), but the reads runtime restarted
|
||||
twice in two minutes "because MESH_TOOL_ENV (mesh-reads (MESH_SECRET_PLACES)) changed": the node-files holder's
|
||||
words are still derived from held modules' stub manifests pass by pass. H-A-306 (2) holds for every runtime process
|
||||
the engine composes from module slices (the reads runtime's secret places included): a held module's slice is copied
|
||||
from what runs. Fixed in the node-engine next, the same kind (fix-a-bug-met-twice). P3.
|
||||
|
||||
Reference in New Issue
Block a user