fix(memory): keep the vault syncing after the Mac changes IP - #54
Merged
Conversation
The vault clone kept the LAN address it was cloned from, so a new DHCP lease left every host-side git call hanging until timeout. That killed the start hook mid-run, `family/brain` was never created, and the curator's push returned 403 on every cycle after that. Separately the working copy sat on a history the remote no longer shared, so the sync failed every 30 seconds and said so only at DEBUG. - Host-side remotes use loopback and the published port, and are re-derived on every `stack up`, so neither a moved IP nor an expired token survives a restart. - A wedged sync now recovers instead of retrying forever: the vault replays local commits onto the remote (a todo tick exists nowhere else) and keeps an unrelated history on a `wedged-orphan-*` branch before resetting; the brain projection realigns and re-projects. - Sync failures are logged where an operator sees them, and a git call that hangs can no longer take a lifecycle hook down with it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new DHCP lease left the memory vault unusable: the clone kept the LAN address (and token) it was cloned from, so every host-side git call hung until timeout. That killed the start hook mid-run, so
family/brainwas never created and the curator's push 403'd on every cycle after. The working copy also drifted onto a history the remote no longer shared, which failed the sync every 30s and said so only at DEBUG.Host-side remotes now use loopback and the published port and are re-derived on every
stack up, so neither a moved IP nor an expired token survives a restart. A wedged sync recovers instead of retrying forever: local commits are replayed onto the remote, an unrelated history is parked on awedged-orphan-*branch before reset, and the brain projection realigns. Sync failures log where an operator sees them, and a hanging git call can no longer take a lifecycle hook down with it.This unblocks writing to the vault from chat (todo ticks were being silently stranded).