fix: stop UI policy deleting static DataSet inventory - #187
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Real field evidence
ARSAS
916a37e3d3c3364bc38a34e4ed2aaaa70a11cac6with ARIEC61850761fa0df9ca84fbe15352d2670f03fddbe8784bastill showed 2 static DataSets / 58 members / 58 semantic descriptors but only 5/58 represented. The diagnostic repeatedly loggedARIEC DataSet authority restored 53 mandatory primary signal(s)while the authoritative device inventory returned to 110 signals and completeness returned to 5/58.Root cause
SasOperationalUiPolicyregistered a globalDataGrid.Loadedhandler, resolved the underlying SignalDefinition source collection, and destructively removed rows rejected bySasOperationalSignalPolicy.IsVisibleusingIList.RemoveAt.That operator policy intentionally accepts exact runtime value leaves. Siemens static FCDA/FCD members in this CID are object-level references with no
daName, so mandatory DataSet rows such asAA1C1F13R4ADD/GGIO6.CBOpndwere correctly restored by ARIEC and then deleted fromdevice.Signalsby UI presentation policy. Collection-change subscription could prune them again after each recovery, explaining repeated +53 restore messages in the field log.Fix
ICollectionView.Filter.DataSetReferenceremains presentation-visible even when the object-level FCD is not an exact runtime leaf..stValor other leaf is fabricated.Regression coverage
CBOpndwith static DataSet membership is visible while the normal leaf policy still rejects it independently;RemoveAt,SchedulePrune, and destructive prune helpers inSasOperationalUiPolicy;Expected next field result
After clean build and fresh CID import:
Physical field validation remains required; CI cannot substitute for the real Siemens CID/UI lifecycle.