Repository navigation
Conversation
…VA-driven controls
FAT Write UX: typed inline value editor and fixed Write action
…ing failed evidence
… altering raw SSOT
… test parallelism
… repair WPF test contract
…iminate per-frame allocations
…Val; normalize CI test line endings
…re explicit one-shot confirmation
…n lease and confirmed native dispatch
…ed message contract
…con and pinned Write caption
…final native DPC Boolean gate
…fore UI authority
…d cache schema read plans
…ng evidence The canonical Windows guard must assert revised distinction between observed RCB instances, live DatSet binding and physical Report ingress.
BCUNR 2026-11-20 follow-up — evidence-backed fix and exact-SHA P9 Windows trialThis user-provided diagnostic is a field follow-up, not a crash or total MMS failure. The P9 58d22be4 trial showed 4/4 selected exact RCBs receiving 16 total Report frames, 125/125 selected points displayed (not 445/445 wire-proven), 2/2 positive enhanced-SBO control terminations and matching Open/Close feedback, 560 observed RCB instances, four initial BRCB BufOvfl flags, and no observed SqNum discontinuity on sequenced streams. The target address also appeared as a local test-PC alias; physical endpoint remains to be verified. IID crosscheck: 39 DataSets, 35 RCB templates × 16 configured slots; 33 DataSets have a matching Verified root cause of mapping undercoverage: initial app field log reported 35/39 no verified RCB-to-DataSet binding despite 560 observed RCB instances. P9 engine sampled only first 64 sorted BRCB instances and 16 numbered slots per family could exhaust this cap on four families. ARIEC #203 (exact SHA Exact app HEAD: ARIEC #203: .NET CI #44720030989 succeeded on attempt 2 (first attempt unrelated timing-sensitive enhanced-SBO negative error test; separate flake audit remains). ARSAS P9 trial Windows CI #44721168600: SUCCESS; 965/965 focused reporting regressions PASS, native bridge and portable EXE smoke PASS.
Never automate control or PurgeBuf to mask BufOvfl. Next field gate: confirm actual endpoint hardware/simulator isolation, open original IID for identity/parity, record live mapped DataSet count versus previous four and the 33 configured design bindings, prove each selected RCB has independent Report ingress, inspect BufOvfl/EntryID, and recheck Toshiba regression. No production promotion or protected merge until qualified. |
…streams BCUNR 33-RCB trial received first Reports after the early 3-second monitor-click deadline. Anchor bounded diagnostic observation to exact completed activation timestamps; summarize 64 scoped RCB groups rather than first 16; keep event log concise; distinguish pending display token from missing wire value. No additional MMS Read, GI, RCB write or process polling. Add 33-RCB, stale/future timestamp regressions.
BCUNR follow-up field validation — P9 33-RCB milestone (2026-11-20)Exact tested EXE: ARSAS Observed progression (not a synthetic test claim)
Root causes for misleading operator diagnostics
Candidate change (no production promotion)ARSAS PR #768 head |
… new activation deadline contract Routed traffic triage correctly requires LastFrameReceivedAtUtc; fix synthetic proof fixture, and update pre-existing static FAT structural assertion to the new bounded post-activation observation API.
P9 diagnostic field follow-up implementation and exact-SHA Windows trial — PASSUpdated PR HEAD:
Canonical pinned-engine Windows build and IO test workflows for this exact HEAD are separate gates; verify their final conclusions independently. |
Final validation of exact P9 diagnostic candidate (2026-11-20)
Field acceptance still pending: new EXE must prove post-activation diagnostic now reflects all 33 RCBs; collect unresolved |
… ingress Only exact schema-resolved scalar Report HasValue with semantic-structured-leaf provenance can preserve literal Unknown; default placeholders, MMS Read, compatibility and stale association remain rejected. No additional MMS IO or RCB/control mutation.
…evidence Evaluate value visibility once per point, require matching live Report reference+FC+association before showing semantic Unknown as populated; thread canonical read-only verdict through FAT/Copy Diagnostic/RCB triage. Add negative/cross-FC/offline/session regression and audit note; zero new MMS I/O.
P9 source-level repair: canonical literal Unknown + association-safe completeness (2026-11-20)Candidate (Draft PR #768, no production merge): exact ARSAS Source-supported root cause and repair
CI and executable
Closure discipline — unresolved field gateThe original SG7_BCU recurrence (2026-10-28: 56/77 and 1/4 RCB) has NOT yet been replayed on this exact P9 engine/ARSAS pair. The newer BCUNR 33/33 stream trial is a different IED and cannot substitute physical SG7 acceptance. BRCB BufOvfl-marked frames, a GI-adjacent SqNum reset, raw Request: keep SG7 P0 issue #707 OPEN until original physical acceptance is demonstrated; do not close it as fixed or promote trial to production based solely on green CI. The PR is ready for exact-head trial, not unconditional production merger. |
P9 canonical verification completed — exact candidate e0cf0aa, 2026-11-20
Close decision: the source defect 'literal |
…riage Display rows may overlap multiple configured RCB DataSets. Preserve independent activation-only RCBs with zero displayed attribution; never borrow member values or ingress proof. Add four-RCB regression.
…tic RCB reporting remains honest Add one-shot exact-reference MMS initial-image reads through the existing per-IED IO ownership gate, with 15s/77-point bounds, association fencing, Stop cancellation and no invented quality, Report attribution or SOE. Preserve RCB traffic status; label Snapshot Read distinctly in Device Explorer. Add SG7 regression and engineering field notes.
SG7_BCU field reproduction and tested P9 repair — 2026-11-20Physical/operator-supplied trial diagnostic: exact nonproduction engine
Exact new ARSAS head:
CI exact-head: P9 Windows trial workflow #44741754523 SUCCESS, 975/975 tests, portable EXE smoke PASS. Artifact #14630533360 SHA-256 Closure gate still blocked: no proof that D01 and I01 began delivering InformationReports, or that B01 delivered three missing process values, or no BufOvfl / replay gap. A one-shot Snapshot Read can populate the visible initial image but must not count as 4/4 Report ingress or close P0 #707. Re-run exact candidate and compare 77 process sources plus per-RCB receipts; gather raw/header evidence for missing GI without blind re-arming. Keep PR draft and issue OPEN. |
Exact-head canonical Windows build has now completed (2026-11-20)Build ARSAS run #44741754423 SUCCESS for same experimental PR head |
Preserve original P9 operator-tested source and all 38 RC commits. Integrate 55 non-overlapping public-site, media and release-governance changes from main plus 7 exact action-version updates. Combine operator screenshot provenance and source-licensed Material vector provenance without overwriting either. 3-way path audit: 63 main deltas, 8 explicitly resolved overlapping paths, 0 candidate-only changes lost; merge remains draft awaiting exact combined Windows CI and IEC 61850 qualification. No stable release or engine repin.
CURRENT MAINLINE INTEGRATION CANDIDATE — 2026-11-21
One authoritative open ARSAS feature PR: P8→P9 reporting, SIEBCU first-connect correction, BCUNR inventory semantics, SG7 four-RCB diagnostics and explicit bounded Snapshot Read. Three old stacked draft PRs #763/#766/#767 were closed as consolidated without merge after verifying exact source ancestry; their branches and original commit SHAs remain auditable.
Current PR base:
main. New combined HEAD:423907349ccc5fe75f60d5af0ddddbde80a2f029, a two-parent, non-forced merge of accepted P9 field-trial sourcea3dca3e8483a7a8b1cb8047e7034db75380f8baaand latest maina0976a0b86dc42945e0d5d9d36724f1e541ef458. Full recursive Git-tree 3-way audit (not compare's 300-file cutoff): 63 main-side file changes, 8 path overlaps manually reconciled (7 one-line GitHub Action updates plus asset provenance), 55 main-only changes retained, 0 candidate-only changes lost. The exact candidate branch is now 0 behind main, 1,685 commits ahead and 569 changed files. This is a large integrated release candidate requiring full regression and review, not a cosmetic backlog cleanup.Existing physical/operator field evidence — BEFORE mainline merge: exact ARSAS
a3dca3e8+ ARIEC trial engine24077e48e393ce3dc2cd1409db6e96f27aa1e368achieved SG7 77/77 report-backed values, 4/4 real RCB ingress (129 InformationReports), 0 pending and 0 cyclic MMS polling. Original P9 Windows exact-head test 975/975 PASS, canonical 3051/3051, pinned engine 24/24, package 6/6, smoke and IO PASS. The merged ARIEC P9 staging source tree was independently verified byte-identical to the trial engine before bringing in current main maintenance. These are historical field + exact-SHA CI facts; they do not certify current combined HEAD.Mandatory next gates: Run combined exact-HEAD
42390734Windows full app/engine/ArdIrec tests, installer + portable smoke, provenance/media guard and workflow integrity. Reconcile engine promotion draft ARIEC #192, and the unresolved P0 command cancellation/Operate stall investigation ARIEC #172. Track SOE buffer-overflow/reconnect continuity separately in ARSAS #769. Preserve typed command/write behavior, bounded report queues, q/t, no hidden polling, no blind GI/PurgeBuf, and source provenance.Publication stop: Public stable v1.6.42 already exists. Current candidate
VERSIONand.release/windows.jsonalso read 1.6.42. Do not republish the same stable tag, run a stable release, or change production engine lock until an explicit next-version decision, combined CI, approved pin/FAT, signed packaging and operator acceptance. This PR stays DRAFT.Historical original PR description (before consolidation)
P9 field-reliability: incomplete MMS inventory vs RCB absence
Evidence (sanitized)
f75e323e, not P9 experimental engine.RptEnabled max=16. The user source is not committed. A missing RCB in partial live discovery is not proof the IED lacks one.Code changes
Stack/merge safety
main, approved engine lock, or stable release.Test expectation
Tests assert that incomplete live evidence cannot claim missing RCB, SCL evidence is correctly scoped, bounded recovery is enabled only for selected unresolved 64-page truncation, the structural Smart Discovery freeze remains, and no polling/ownership side effects are added.
SG7 field acceptance update — 2026-11-21 (trial-only)
a3dca3e8483a7a8b1cb8047e7034db75380f8baa+ staged ARIEC24077e48e393ce3dc2cd1409db6e96f27aa1e368; same identity as P9 portable trial run #44741754523. Operator diagnostic generated 2026-11-21 02:30 WIB.cyclic MMS process polling=0. Initial-image D01 remainsNOT ATTRIBUTEDbecause of overlapping selected point rows; 37 independent D01 Report frames are nevertheless proven.f75e323e9f8443aa20e0a3818a1d5d77255b2c0funchanged,mainunchanged. No automatic merge or production promotion authorized by this field success. Exact candidate Windows CI: P9 focused 975/975, canonical 3,051/3,051, pinned engine 24/24, packaging 6/6, IO+interop SUCCESS, portable smoke PASS.Scope distinction: SG7 missing-values/RCB-ingress incident now has qualifying positive P9 field evidence; #769 owns separate continuity/reconnect concerns. This is a nonproduction test acceptance, not stable release qualification.