-
Notifications
You must be signed in to change notification settings - Fork 35
Add bounded chat-list storage pages (C4 M1) #1778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
erskingardner
wants to merge
5
commits into
master
Choose a base branch
from
codex/1777-c4-m1-chat-list-pages
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
fc32b0e
feat: add bounded chat list storage pages for C4 M1
erskingardner 51c98c7
fix: support anchored page recovery and bound navigation write work
erskingardner f813315
fix: reconcile mixed-case lifecycle ids and batch chat page reads
erskingardner 1719ee1
fix: rebuild cached pin order once per command
erskingardner c666d50
test: drive scheduled convergence quanta before asserting queued output
erskingardner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two divergent truths for the same three fields, and a macro to express the divergence.
chat_list_pagenow returnsCOALESCE(ag.archived, row.archived)whilechat_list_row/chat_list_rowsstill returnrow.archived, so the two read paths can disagree aboutarchived,pending_confirmationandself_membershipfor the same conversation.accepting_an_archived_invite_preserves_archive_and_source_fieldsasserts that divergence directly:I checked why the overlay is load-bearing:
set_group_self_membership(and the archive writers) updateaccount_groupswithout refreshing thechat_list_rowsprojection, so the projection really can lag. But that means this PR routes around a stale-projection bug in a new API instead of fixing it, and leaves every existing caller reading the stale value.Migration 0070 already installs
chat_list_keys_account_groups_{INSERT,UPDATE,DELETE}firing on exactlyarchived, pending_confirmation, self_membership. Extendingrefreshto also copy those three columns intochat_list_rowswould:row.archived/row.pending_confirmation/row.self_membershipdirectly,chat_list_columns!,CHAT_LIST_PAGE_SELECT_LISTand the whole diff to this file.If there's a reason the projection deliberately must not track the source here, that belongs in a comment — right now the macro documents the mechanism but not the motivation. And if the overlay stays, the
pinnedflag is still read fromchat_pin_positionswhile ordering uses the projectedlist_pin_ordinal, which is a third instance of the same source/projection split in one row.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Documented the compatibility reason beside CHAT_LIST_PAGE_SELECT_LIST in
f813315a. The new page contract reads committed account-source state immediately. Legacy readers retain their existing projector publication timing. Copying these fields into legacy rows from new triggers would alter existing reader/subscription behavior without their associated runtime refresh notifications. #1777 explicitly leaves legacy behavior unchanged in M1 and assigns authoritative command/invalidation integration to M2. I am keeping that migration boundary instead of silently expanding this storage PR into a legacy publication change. Pin source and cached ordinal remain maintained in the same source transaction and are checked by the pin-gap/recreation tests.