Repository navigation
Change CRDT logic to use tombstoning instead of ad-hoc resurrection - #4636
Merged
Merged
Conversation
Member
|
Just in time for spooky season! 🪦🧟 |
Contributor
There was a problem hiding this comment.
3 issues found across 24 files
Confidence score: 2/5
attributes.rsmakes existing Postcard registry snapshots fail to deserialize;#[serde(default)]does not preserve compatibility with positional binary encoding. Add a legacy decoder or migration.to_runtime.rscan revive a deleted nested network on the next commit when a live owner still references it. Preserve the tombstone when staging from runtime.staging_and_reopen.rsnever reopens the document, so it does not verify the stated reopen behavior. Reopen throughinto_storage/open_inand assert the registry matches.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="document/format/tests/staging_and_reopen.rs">
<violation number="1" location="document/format/tests/staging_and_reopen.rs:39">
P2: This test never reopens the document, so it only verifies in-memory staging and cannot validate the stated reopen behavior. Move the storage through `into_storage`/`open_in` and assert the reopened registry matches the staged batch.</violation>
</file>
<file name="document/graph-storage/src/to_runtime.rs">
<violation number="1" location="document/graph-storage/src/to_runtime.rs:177">
P1: This renders a deleted nested network whenever a live owner still references it. `stage_from_runtime` converts that runtime network back to a live entry and emits `AddNetwork`, reviving the tombstone on the next commit; preserve the removed state across this round trip.</violation>
</file>
<file name="document/graph-storage/src/attributes.rs">
<violation number="1" location="document/graph-storage/src/attributes.rs:18">
P1: Adding this positional field makes existing Postcard registry snapshots fail to deserialize; `#[serde(default)]` does not make the binary struct encoding backward-compatible. Add an explicit legacy decoder or migration before changing this persisted shape.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
TrueDoctor
force-pushed
the
graph-storage-2-lww-existence
branch
from
October 2, 2026 21:19
32b18d2 to
8af650b
Compare
timon-schelling
approved these changes
Oct 4, 2026
timon-schelling
left a comment
Member
There was a problem hiding this comment.
My main concern is having tombstones in the registry when saving without history. We could put them in a separate path right?
see the rest of the comments, in general LGTM
TrueDoctor
force-pushed
the
graph-storage-2-lww-existence
branch
from
October 5, 2026 20:40
8af650b to
3ac7aa7
Compare
TrueDoctor
force-pushed
the
graph-storage-2-lww-existence
branch
from
October 5, 2026 21:07
3ac7aa7 to
db10f2b
Compare
Contributor
There was a problem hiding this comment.
1 existing issue remains and no new issues found across 21 files
Confidence score: 2/5
document/graph-storage/src/attributes.rschanges the positionalAttributesencoding without changing how existing v1 registries are decoded, so stored data may fail to decode or be read incorrectly. Add a versioned decoder or migration before changing this encoding.
Requires human review: Auto-approval blocked because this review re-detected 2 unresolved issues already reported by Cubic.
Re-trigger cubic
TrueDoctor
force-pushed
the
graph-storage-2-lww-existence
branch
from
October 7, 2026 15:54
db10f2b to
60cca98
Compare
…presence stamps and tombstones
TrueDoctor
force-pushed
the
graph-storage-2-lww-existence
branch
from
October 7, 2026 15:57
60cca98 to
4e1da8f
Compare
6 of 51 tasks
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.
No description provided.