-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: NamespaceSyncState improvements #339
Conversation
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.
one comment about the caching that may require changes
looks like tests are failing for something legitimate |
oops sorry I should have run the whole test suite. My change to a test helper function was breaking a test elsewhere in the code. |
* main: feat: NamespaceSyncState improvements (#339) chore: update better-sqlite3 to 8.7.0 (#337) chore: update @mapeo/crypto to latest (#336) fix: write own device info when creating and adding projects (#297) Feat: add DataStore.writeRaw method (#334) feat: Add NamespaceSyncState (#313) chore: run CI on PRs against any branch (#330) feat: add capabilities.getAll() (#326)
Had originally omitted the sums of peer sync states for cores in a namespace because we don't need it for the UI, but it turns out we need it for the internal sync control because we need the state of each peer before we allow moving to the next stage of sync.