- use a dedicated context "dropped off" the TestChainLoad instance - encode the node-idx into the InvocationInstanceID - build an invocation- and a planning-job-functor - let planning progress over an lib::UninitialisedStorage array - plant the ActivityTerm instances into that array as Scheduling progresses |
||
|---|---|---|
| .. | ||
| application | ||
| steam | ||
| vault | ||
| DIR_INFO | ||