release 0.3.17 plan: the Mac row; 0.3.17 live
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
parent
4b597d73ae
commit
3fa25b2d23
1 changed files with 6 additions and 1 deletions
|
|
@ -107,4 +107,9 @@ The object on all three: the live manifest's consensus.override (16 fields, floo
|
|||
|
||||
The `restart --what miners` job ran 05:18:09Z ("miners restarted"); the 05:32Z dump reads the same as 05:15Z: mining "waiting", paused false, every enabled card "faulted: no status line from the miner for 90 s (restarted once already)", pid 0, faults 0, hash 0.0, program "next program not known yet" (boundary 255,600, 36 minutes off), node synced at DAA 253,048 with 5 peers. Main's rule: PC 1 waits for the project lead with these lines; the fix is miner-ui-4 bac43ac4 in 0.3.18 (the watchdog releases a sync-time silence fault when the node syncs and starts the card again). The dumps: scratchpad/r0317hf/pc1-fault/state-mining-0515Z.json and state-mining-after-restart.json. Proving on PC 1 unaffected throughout.
|
||||
|
||||
(the Mac row closes the table)
|
||||
## 8. The Mac, and "0.3.17 live" (05:4xZ)
|
||||
|
||||
Mac (d937c69d): app 0.3.17 applied 04:51:43Z; own node pid 20371, the bundle's igneumd carries 5899f603 (2 marks) and the igneum-pow link (8 paths), consensus_digest eada4bda, override.json = the live sixteen-field object; the node caught up from DAA 119,362 through the headers batch and the block replay (93,704 of 118,131 blocks at 05:30Z, about 4 a second) and read synced at 05:36Z: DAA 254,195, headers equal blocks at 121,741, 4 peers. The miner stays paused on the project lead's order.
|
||||
|
||||
**0.3.17 is live** on every node that can take it: the 14 standing fleet boxes, the Mac, PC 1 (node; the workers wait for the project lead), the observer node, node 1 and the seed, all on commit string 5899f603, digest eada4bda, igneum-pow linked. PC 2 is offline since 02:00 UK (host unreachable) and takes the manifest when it returns. The canary's relay and poison cases run on as confirmation (verdict about 05:55Z); a FAIL there is a 0.3.16-with-the-fix rebuild by main's rule, not a rollback. The Discord card posts on this line.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue