Repository navigation
Harden Dynamic DataSet and RCB ownership safety - #46
Merged
Merged
Conversation
masarray
marked this pull request as ready for review
August 11, 2026 00:11
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.
Scope
Close the three live Dynamic Reporting safety findings that remained on current
mainafter #31/#32:owned_onlydeletion therefore cannot carry stale ownership into a later MMS association.RptEna=false,Resv=false, orDatSet=""writes. RptEna/Resv cleanup remains owned byMmsReportSubscriptionRuntime; failure-path DatSet unbind is permitted only when the subscription event record proves this run successfully wrote DatSet, and DataSet deletion is withheld if RCB cleanup remains pending.Regression coverage
attribute_writtenevent.Lineage
Based directly on current
mainata92c42a, which already contains merged Smart Control #43, static reporting, Dynamic reporting, and MMS file transfer. This PR does not re-merge or retarget the historical control stack.