From 51ca048d34cb39f6889ba77ec4f2982f42e82dde Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Wed, 21 Jan 2026 10:23:29 +0000 Subject: [PATCH] issue: update b4d0 - configuration deployed and service restarted --- b4d0-failed-historic-sync-batches-not-retried.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/b4d0-failed-historic-sync-batches-not-retried.md b/b4d0-failed-historic-sync-batches-not-retried.md index 0380621..5a8746e 100644 --- a/b4d0-failed-historic-sync-batches-not-retried.md +++ b/b4d0-failed-historic-sync-batches-not-retried.md @@ -38,6 +38,15 @@ When syncing from a relay that doesn't support negentropy (NIP-77), historic syn - Completed: Applied workaround configuration to archive service (disable negentropy) - Next: Implement proper retry mechanism for failed batches +### 2026-01-21 [Session 11:22] +- Completed: Updated NixOS configuration with `syncDisableNegentropy = true` +- Completed: Deployed configuration to vps1 (commit 37f30bf) +- Completed: Service restarted successfully with REQ+EOSE sync method +- Decision: No session files to delete - sync state is in-memory only +- Verified: Historic sync completed with `sync_method=ReqEose`, `had_failures=false` +- Verified: State events (kind 30618) are being received from relay.ngit.dev +- Next: Monitor sync completeness and verify all historic events are retrieved + ## Notes - Discovered during relay.ngit.dev migration analysis