Proposal 0030: a roll-up's status is relinquished, not only set - #60
Merged
Conversation
This was referenced Sep 6, 2026
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
1 participant
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.
A
rollupsentry withcapacityandstatusmoves the parent tostatusWhenFull/statusWhenPartialas the summed children arrive; the text says nothing about the sum shrinking, and an implementation reading it literally leaves a fully refunded invoice PAID. This proposal makes the way back normative: the first move into a roll-up-owned status records the displaced status, a sum back at zero restores it, only roll-up-owned statuses are relinquished, and there is nostatusWhenEmpty. Implementation: eclipse-dirigible/dirigible#7016.