-
-
Notifications
You must be signed in to change notification settings - Fork 126
feat!: replace history sync events with lazy blob + perf optimizations #533
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
Merged
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
932816b
feat!: replace per-conversation history sync events with single lazy …
jlucaso1 146bf55
fix: always serialize cheap metadata in LazyHistorySync
jlucaso1 9916b2d
docs: warn about memory cost of LazyHistorySync::get() on large blobs
jlucaso1 a718f4b
perf: optimize history sync allocations and remove channel overhead
jlucaso1 bd71f0f
fix: address review findings — safety, dead code, allocations
jlucaso1 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
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.
Event::HistorySyncmetadata is populated withnotification.sync_type().into(), but the prost-generatedsync_type()accessor returns the default enum when the field is unset or contains an unknown value. That means new/forward-compat server sync types get silently rewritten (typically toInitialBootstrap) before handlers see them, so consumers branching onhs.sync_type()can take the wrong path. Prefer preserving the raw field value (notification.sync_type) and representing it as optional/raw inLazyHistorySyncmetadata.Useful? React with 👍 / 👎.