Closed EvanHahn closed 4 months ago
These tests have been very flaky. After a few hours of investigation it seems that peers weren't synced before someone left the project, which caused waitForSync to hang indefinitely.
waitForSync
We likely want our leave code to be more robust. In the short term, however, I think it's worth fixing these tests. (See https://github.com/digidem/mapeo-core-next/pull/469#issuecomment-2050255602 for these "make it more robust" tasks.)
Closes #540.
These tests have been very flaky. After a few hours of investigation it seems that peers weren't synced before someone left the project, which caused
waitForSyncto hang indefinitely.We likely want our leave code to be more robust. In the short term, however, I think it's worth fixing these tests. (See https://github.com/digidem/mapeo-core-next/pull/469#issuecomment-2050255602 for these "make it more robust" tasks.)
Closes #540.