jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Refresh queue and region companion-set ownership

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 17:34:44 -07:00
commit 9d8b4e4031
2 changed files with 36 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

12
crates/rrt-runtime/src/smp.rs
View file

@ -4254,6 +4254,7 @@ fn build_region_service_trace_report(
"that broader restore strip now also has one grounded later region-local sweep: at 0x00444b08 it re-enters the live region collection through 0x00421ce0, which walks live records via 0x518380/0x518140 and dispatches 0x0041fb00 per record".to_string(),
"the checked-in atlas already grounds 0x0041fb00 as the class-0-only default-region helper under the same family, and 0x00421730 as the later raster finalizer that repopulates [world+0x212d] from class-0 region ids".to_string(),
"direct disassembly now tightens that later sweep too: 0x0041fb00 exits immediately for nonzero [region+0x23e], while 0x00421730 clears the per-cell region word at [world+0x212d]+cell*4+1, seeds cached bounds-like fields [region+0x242/+0x246/+0x24a/+0x24e/+0x252], and only then enters the class-0 path that consumes [region+0x256] and the coordinate helpers 0x00455800/0x00455810".to_string(),
"the companion region-set root is runtime-owned now too: direct disassembly of the broader bring-up strip at 0x00448740..0x0044881f shows 0x006cfc9c being allocated through 0x53b070 and constructed through 0x00487bd0 before later rebuild passes run, so the 0x00487650/0x004881b0 companion path is operating on a runtime-owned helper collection rather than a hidden save-owned latch seam".to_string(),
"the later restore-band siblings are tighter now too: 0x00487de0 clears the prior chunked border queues through 0x00533cf0, builds a small per-region id map from [region+0x00]/[region+0x35] keyed by class [region+0x31], scans the live world raster at [world+0x2131], and appends fresh border-segment rows through 0x00536ea0 without touching [region+0x25e/+0x276/+0x302/+0x316]".to_string(),
"the neighboring world-grid reseed 0x0044c4b0 is tighter now too: it clears bit 0x10 across the live grid byte at cell offset +0xe6, then walks the live region collection at 0x0062bae0, admits only class-0 records via [region+0x23e], resolves one representative center cell through 0x00455f60, and marks that same bit back on, which again reads as raster presentation state rather than pending/completion latch restore".to_string(),
"the companion region-set rebuild above that border pass is narrower now too: 0x00487650 is only a small constructor wrapper over 0x00487540 that seeds [region+0x00] from the caller-supplied id, while 0x004881b0 rebuilds [region+0x3d] from the world raster histogram, zeroes [region+0x41], folds class-0 children back into parent [region+0x41] through [region+0x35], and then tails into the border emitter on 0x006cfc9c via 0x00487de0".to_string(),
@ -25599,7 +25600,7 @@ mod tests {
);
assert_eq!(
trace.candidate_consumer_hypotheses[2].status,
"secondary_candidate_after_attach_rebuild"
"secondary_candidate_after_pending_service"
);
assert_eq!(
trace.candidate_consumer_hypotheses[1].status,
@ -25642,6 +25643,15 @@ mod tests {
.any(|line| line.contains("0x00421730")
&& line.contains("[region+0x242/+0x246/+0x24a/+0x24e/+0x252]"))
);
assert!(
trace.candidate_consumer_hypotheses[1]
.evidence
.iter()
.any(|line| line.contains("0x00448740..0x0044881f")
&& line.contains("0x006cfc9c")
&& line.contains("0x53b070")
&& line.contains("0x00487bd0"))
);
assert!(
trace.candidate_consumer_hypotheses[1]
.evidence