npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/tests/sync/catchup.rs, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=master2025-12-11T15:02:33+00:00docs(tests): replace catchup.rs test with documentation2025-12-11T15:02:33+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-11T15:02:33+00:00urn:sha1:3d11a99b4adc9ad900190b797e6d6dc1f97116fa
The catchup sync mechanism (reconnection with since filter) is implemented
in src/sync/mod.rs handle_connect_or_reconnect(), but cannot be reliably
integration tested with current infrastructure:
- TestRelay uses in-memory database (events lost on stop)
- No way to force WebSocket disconnection without stopping relay
- Stopping syncing relay creates new instance (fresh sync, not catchup)
Convert the skeleton test file to comprehensive documentation explaining:
- How catchup sync works (since filter on reconnect)
- The 15-minute quick reconnect window logic
- Why integration testing is not feasible
- Alternative approaches that could enable testing
- Related tests that cover adjacent functionality
refactor(tests): extract shared create_repo_announcement helper2025-12-10T16:59:09+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-10T16:59:09+00:00urn:sha1:cbed48d5a20b646a5bcc23e907d6163a3a8d36c5Phase 8: Create catchup sync stub test2025-12-10T16:31:47+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-10T16:31:47+00:00urn:sha1:5f3c8b7085f6652fdde4443983df0aad561e3c67