npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/tests/purgatory_persistence.rs, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=master2026-02-26T15:42:09+00:00chore: apply cargo fmt and fix clippy warnings2026-02-26T15:42:09+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-26T15:42:09+00:00urn:sha1:9d86cf15f0275ffeee4519bd054e3b61dc8992ac
Fix pre-existing clippy lints:
- &PathBuf -> &Path in audit_cleanup.rs
- too_many_arguments on process_newly_available_git_data,
process_purgatory_announcements, and HttpService::new
- clone_on_copy for PublicKey (Copy type) in purgatory cleanup loop
Merge master into 3ca0-announcements-purgatory2026-02-23T15:20:59+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-23T15:20:59+00:00urn:sha1:113928aa84894ea8f65c247d9987527e792b32a9persist and restore announcement events across graceful restarts2026-02-23T15:08:37+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-23T15:08:37+00:00urn:sha1:26f608e5011b9d1ad6036da75b89272835e69695
Extends purgatory persistence to include announcement purgatory entries.
On graceful shutdown, non-soft-expired announcements are serialised to
purgatory-state.json alongside state/PR/expired events; on startup they
are restored, skipping any entry whose bare repo path no longer exists.
Updates purgatory-design.md to reflect that purgatory persists through
graceful shutdown and documents the new PurgatoryState disk format.
Adds create_announcement_event helper to purgatory_helpers and three new
integration tests in purgatory_persistence covering the full save/restore
cycle, missing-repo skip, and the combined roundtrip with all entry types.
feat: implement announcement purgatory core (breaks archive sync test)2026-02-13T17:29:23+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-13T13:24:46+00:00urn:sha1:1d09e4bdea7e328cf2740818df9df660c5532a99
Route new announcements to purgatory instead of accepting immediately.
Announcements are promoted to the database when git data arrives,
ensuring we only serve announcements for repos with actual content.
Implemented:
- AnnouncementPurgatoryEntry type and DashMap store
- Route new announcements to purgatory (replacement announcements skip)
- Promote announcements on git data arrival (process_purgatory_announcements)
- Authorization checks purgatory announcements (fetch_repository_data_with_purgatory)
- State policy uses purgatory announcements for maintainer validation
- Cleanup task handles announcement expiry
- Updated count()/cleanup() to 3-tuples
Known broken:
- test_archive_read_only_creates_bare_repo fails: sync module does not
treat purgatory announcements as confirmed repos, so per-repo sync
(state events, PRs) is never triggered for purgatory announcements
- Announcement persistence (save/restore) not implemented
- SyncLevel (StateOnly vs Full) not implemented
- Soft expiry two-phase not implemented
- Expiry extension on state event / git auth not wired up
Merge relay.ngit.dev migration: bug fixes and migration tooling2026-02-03T15:18:23+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-03T14:50:22+00:00urn:sha1:874a8abe1d076cfafd9baf919ec23d7d58200698
This merge includes critical bug fixes and comprehensive migration tooling
developed during the relay.ngit.dev migration effort.
Bug Fixes:
- Fix git protocol error handling to return HTTP 200 with ERR pkt-line
- Fix naughty list false positives and DNS failure identification
- Fix database query filters in load_existing_events (remove .since())
- Fix OID fetch tracking to distinguish 0 OIDs from successful fetches
- Fix purgatory event source tracking for filtered expiry logging
- Implement OID retry logic for 'not our ref' errors
Migration Tools & Documentation:
- Complete 5-phase migration analysis pipeline with orchestration script
- Phase 1: Event fetching from source relay
- Phase 2: Git sync verification
- Phase 3: Categorization and relay comparison
- Phase 4: Log extraction (parse failures, purgatory expiry)
- Phase 5: Action classification for migration decisions
- Comprehensive migration guide with lessons learned
- Troubleshooting guide for permission and corruption issues
Configuration:
- Add NGIT_LOG_LEVEL configuration option
- Update git throttle limits to 60/minute
- Improve logging throughout for better observability
chore: cargo fmt2026-01-21T13:40:10+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-21T13:40:10+00:00urn:sha1:5913c5aab4d22fcb2984e9a34b439190639b346dfeat(sync): add rejected events cache persistence and integrate with shutdown/startup2026-01-14T10:19:18+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-14T10:19:18+00:00urn:sha1:b101afa00bc28e1b55286145cb81e32a5b3decc9
Implement save/restore functionality for rejected events cache and
integrate persistence with relay shutdown/startup lifecycle. Both
purgatory and rejected cache now survive relay restarts.
Key features:
- Serialize rejected events cache to JSON (rejected-events-cache.json)
- Save both hot cache (2min, full events) and cold index (7day, metadata)
- Restore with downtime adjustment (preserves remaining TTL)
- Graceful degradation (missing/corrupted files don't crash)
- File cleanup after successful restore
- Automatic restoration in SyncManager::new()
Integration:
- Shutdown hook saves both purgatory and rejected cache
- Startup hook restores both and re-queues repositories
- Non-fatal errors (logs warnings, continues on failure)
Files:
- src/sync/rejected_index.rs: save_to_disk/restore_from_disk methods
- src/sync/mod.rs: SyncManager integration and auto-restore
- src/main.rs: Shutdown/startup hooks for both caches
- tests/purgatory_persistence.rs: 17 integration tests
Tests: 13 unit tests + 17 integration tests covering full lifecycle