Repository navigation
M2.17-D Field convergence: GoCB passive evidence, SGCB initial status, RCB/Read correctness - #606
Conversation
|
Reconciliation finding (2026-10-26): KEEP OPEN — unproven unique regression delta. The original #606 source |
Reconciliation D1 — 7-test historical coverage map (2026-10-26)Disposition: D — KEEP OPEN until the two incomplete assertions are resolved. Old test blob
Safety: no code or test was ported without checking new APIs; raw allData is always labeled unbound and must never be promoted to FCDA or MMS ledger. Never merge the historical file as-is (obsolete Follow-up: ask canonical IED Browser/GOOSE owner to trace decoder invariants for wire count/order/missing sentinel and add minimal test-only cases for any true missing behavior. Likewise prove/fence wrong-domain SGCB (a syntactically valid block from another model domain must not silently become current association authority). Keep #606 open pending focused tests and required CI; no physical GOOSE/safety acceptance implied. |
Reconciliation D3 — focused rescue is now a separate current-RC draft PRDisposition: KEEP historical #606 OPEN (no blind cherry-pick / no ancestry-only closure). The two unique current-tree gaps identified in D1 7-method matrix now have a narrowly scoped corrective candidate: #753, branch
|
D5 source-test continuity: #606 stays OPEN until current RC integration and seven-case adjudicationExisting historical head: Real current-tree rescue: draft #753 has progressed beyond D3: new exact head
Original seven-assertion disposition matrix:
CI truth: previous 5-file #753 exact head Safety: No #606 source branch mutation, no main, no engine lock, no MMS Write/Operate, no public release. Keep #606 OPEN until #753 exact-head CI, owner/GUI parity review, approved RC integration, and physical GOOSE/SGCB validation gates as applicable. |
…ssion recovery, exact-head CI gates
D6 acceptance update — #753 current-tree rescue exact-head Windows+SCL CI fully green, #606 still OPENThe current canonical six-file recovery #753 Disposition: KEEP #606 OPEN, historical 7-test source preserved, no blind cherry-pick. #753 remains DRAFT / UNMERGED until RC owner accepts deliberately changed visual RCB flag nesting/section default, shared GOOSE subscriber boundary and exact-source #753 integration. Physical IED GOOSE/SGCB FAT, R7/R10 promotion and command #615 remain separate. Success on draft code is not synonymous with accepted release, nor proof of physical wire transmission. |
|
D28 legacy candidate archived, not merged. Per the operator's explicit instruction, the latest accepted ARSAS working evidence is the baseline; no new hardware/packet capture cycle is required for cleaning up outdated PRs. Historical candidate |
M2.17-D / BCUGE field-feedback correctness slice — stacked draft on #605
This patch follows the physical operator screenshots. It deliberately fixes documented seams, not an entire UI repaint or a fabricated "all data complete" claim.
Root causes and repairs
IedBrowserGooseInspection.Selectrejected every wire frame when the online GoCB discovery did not disclose its DataSet reference. Permit a single exact received GoCbRef (matching declared GoID/AppID/confRev when available) to supply its ACTUAL PDU DataSet reference. A conflicting known DataSet, different IED model, APPID, rev, or ambiguous duplicate still fails closed. Reuse the existing GOOSE Sniff subscriber via a visibleSubscribe GOOSEaction; never start a second reader/decoder/cache. For missing or conflicting FCDA directories, surface original allData positions as explicitlyWire entry #N (unbound), never name them as model FCDA or borrow sibling FC. Do not infer MMS GoEna from passive reception.Control Block attributesinstead of becoming separate Section siblings. The existing engine flag codec and shared section projection remain authoritative; no bit decoder added.IsMonitoringchanges. Rebuild existing glyphs only when the actual activated RCB identity set changes. Explicit read-only RCB checks are additionally fenced against association/schema swap. RCB use by another client still requires a real read-only status check, never inference from name or missing report frames.Tests and safety
Seven added focused regressions covering selected physical-style GoCB + subscriber allData, missing directory, duplicate/conflicting frame rejection, bounded exact SGCB read priorities and unauthorized FC rejection, report-control collapse hierarchy, existing subscriber use, RCB association fences and file indent. No engine re-pin, no native library change, no protocol replacement, no GOOSE emission, no MMS writes, no auto Read All.
What this does NOT claim
Keep draft; merge/promotion only after exact-SHA CI and physical interoperability review.