npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/tests/common/relay.rs, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=master2026-02-23T12:48:26+00:00refactor: replace inline purgatory sync registration with timer-only approach2026-02-23T12:48:26+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-23T12:48:26+00:00urn:sha1:f62ef12fb84e2210f9a0a67a5e1e574a8ee66c16
Remove the redundant inline kind-30617 registration block from the sync
event loop and the three is_generic/recompute_new_sync_filters_for_relay
calls from confirm_batch error paths. The purgatory announcement sync
timer (run_purgatory_announcement_sync) is now the sole registration path.
Consolidate NGIT_SYNC_BATCH_WINDOW_MS and NGIT_PURGATORY_SYNC_INTERVAL_MS
into a single NGIT_TEST=1 flag that sets both timers to 200ms, replacing
two ad-hoc env vars with one reusable test-mode flag.
test: rewrite PR sync tests to reflect purgatory-first announcement flow2026-02-18T17:12:27+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T17:12:27+00:00urn:sha1:07c8c00274298e90654207d8baceb1089514ccae
The tests now correctly reflect the actual purgatory behavior:
1. Announcement goes to purgatory (StateOnly) - not immediately accepted
2. State event goes to purgatory
3. Git push promotes announcement to Full and releases state event
4. PR event is sent AFTER announcement promotion (accepted since repo is Full)
5. PR commit push releases PR event from purgatory
This matches the design: announcements require git data validation before
being promoted to the database, which means PR events can only be accepted
for repos with promoted announcements.
Also routes relay stdout to /tmp/relay-{port}.log for easier debugging.
fix: archive_read_only creates bare repos for archived announcements2026-01-19T15:04:00+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-19T14:25:27+00:00urn:sha1:9372ad649b6c438b1e4645f1dbe95c0f648bb80d
Combined Accept and AcceptArchive match arms in builder.rs to ensure
bare repositories are created for both cases. Previously AcceptArchive
had duplicate code that didn't call ensure_bare_repository().
Also includes:
- Config fix: effective_git_data_path() respects explicit paths with memory backend
- TestRelay: Added git_data_path() and archive config support for testing
- Integration tests for archive_read_only behavior
chore: cargo fmt2026-01-08T00:50:54+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-08T00:50:54+00:00urn:sha1:f75e1c59aacf5ce668fd327e4e3d827511661c2atest: add test_state_event_syncs_from_remote integration test2026-01-07T15:39:48+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-07T15:39:48+00:00urn:sha1:1db877d53c4ff45971c69fecc5165c352ec316c9
Implements Phase 3 of the purgatory sync integration test plan.
Key changes:
- Add immediate sync triggering for sync-received events that go to
purgatory (instead of default 3-minute delay for user-submitted events)
- TestRelay now respects RUST_LOG environment variable for debugging
- New test verifies end-to-end flow: state event syncs from source relay,
enters purgatory, git data is fetched from source's clone URL, and
event is released and served
fix: resolve all fmt and clippy warnings2025-12-11T16:53:03+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-11T16:53:03+00:00urn:sha1:2a9160836bb87fdea3ae891563b0169c68d1c2ab
Main lib (src/):
- Add #[allow(dead_code)] for build_info field (stored to prevent Prometheus unregistration)
- Add #[allow(dead_code)] for first_seen field (reserved for future rate limiting)
- Replace .or_insert_with(RelaySyncNeeds::default) with .or_default()
- Replace manual div_ceil implementations with .div_ceil(100)
Test code (tests/):
- Replace .expect(&format!(...)) with .unwrap_or_else(|_| panic!(...))
- Remove needless borrows in fetch_metrics() calls
- Add #[allow(dead_code)] and #[allow(unused_imports)] to test helpers module
grasp-audit:
- Apply cargo fmt to fix formatting
sync: test sync works without negentropy and add disable option in sync2025-12-11T16:46:01+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-11T16:45:34+00:00urn:sha1:52489d3b1a7d79e164b4cc901b53fd06c05ce1b1sync: add sync_base_backoff_secs config for better testing2025-12-11T11:57:36+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-11T11:57:36+00:00urn:sha1:4941490233a728bc7c64fa80a53d15f772a1219ffix(sync): improve metrics recording and connection failure detection2025-12-11T11:19:38+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-11T11:19:38+00:00urn:sha1:c82684092c7b4f81e49833b0888500fcb9851218
Changes:
- Fix connection attempt metrics: record success/failure based on actual
connection result instead of pre-emptively recording failure
- Add health tracker integration on connection failure: call
record_failure() and record_health_state() in error path
- Add connection verification in relay_connection.rs: wait 500ms after
connect() then verify is_connected() to detect silent failures
- Add configurable disconnect check interval via
NGIT_SYNC_DISCONNECT_CHECK_INTERVAL_SECS env var
- Update TestRelay with fast test settings: startup_delay=0, jitter=0,
disconnect_check_interval=1s
- Add debug output to metrics tests for investigation
Note: Tests may still fail due to 5-second base backoff in health tracker.
A follow-up task will add NGIT_SYNC_BASE_BACKOFF_SECS config parameter
to allow faster test cycles.
Related: metrics-wiring-plan.md Tasks 1 & 2
sync: fix connection registration issue2025-12-10T14:37:19+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-10T14:36:06+00:00urn:sha1:8148c27a1350189046bc8e215f29f918dd8747f5