Repository navigation
Bump embedded furrow to v0.3.4 (prune abandoned capture plans) - #1974
Merged
Merged
Conversation
AbirAbbas
added a commit
that referenced
this pull request
Oct 26, 2026
…urrow v0.3.4 Brings the workspace-ownership branch up to dev cf282dd, which adds the Raft relay (#1950), the two-computer fixes (#1967), #1972, #1974 and #1976. - directory record types are now clusterstate aliases, so frame hints move into the replicated state machine: FrameHint and the frame_hints field on Cell, CellInit and Publish, bounded deterministically in the shared rules, dropped from listings and kept on single-cell reads. Signed v1 publishes with hints are accepted; unknown fields are still refused; existing canonical bytes are unchanged and no schema or protocol version moves. - every take path records the send lease, including the workspace-set and identity-adopting restores; an already-held chat keeps its hold when the record fails. - a removed computer cannot take through the folder-mapping road either, and unsent words and the pending send survive the root chooser. - the seal refuses a folder holding home before taking the checkpoint lock. - furrow pin follows dev at v0.3.4, which contains v0.3.2's non-mutating SQLite capture. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
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.
Pins the embedded engine to furrow v0.3.4, which carries Agent-Field/furrow#20.
Why
furrow deletes a capture plan only when a seal succeeds. Plans that no caller seals (a re-plan, a timeout, an engine that exits mid-save) were never removed. On one machine 43 of them added up to 98 GB under
~/.codeaf/v3/stores/shared/store-v1/workspaces/*/capture-plans/.What changes
internal/furrowbin/pin.json→ v0.3.4 (regenerated from the release's SHA256SUMS; same platform set).SealWithin), so a live plan is never pruned; a pruned one fails with the existing "re-plan" error.Verification (Spark)
furrow 0.3.4.make checkresult posted below.🤖 Generated with Claude Code