-
Notifications
You must be signed in to change notification settings - Fork 1
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
Sync/ Device discovery inconsistent #872
Comments
I can't reproduce this issue on the backend. I wrote this test to simulate the bug we were seeing: test('issue 872', async (t) => {
const managerCount = 4
const managers = await createManagers(managerCount, t)
const [invitor, ...invitees] = managers
const disconnectPeers = connectPeers(managers)
t.after(disconnectPeers)
const projectId = await invitor.createProject({ name: 'Mapeo' })
await invite({ invitor, invitees, projectId })
const projects = await Promise.all(
managers.map((m) => m.getProject(projectId))
)
await waitForSync(projects, 'initial')
for (const project of projects) {
const { remoteDeviceSyncState } = project.$sync.getState()
const otherDevices = Object.keys(remoteDeviceSyncState).length
assert.equal(otherDevices, managerCount - 1)
}
}) I don't think this test is worth including because it's so specific, but I tweaked an existing test in #964. Either this is no longer a bug, it's a frontend-only bug, or the bug exists elsewhere. |
EvanHahn
added a commit
that referenced
this issue
Nov 18, 2024
Andrew was still able to reproduce this. I was hopeful that we'd fixed it, but alas. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details : https://www.notion.so/digidem/Sync-Device-discovery-inconsistent-10c1b08162d580099a26fdeb94138c5c
The text was updated successfully, but these errors were encountered: