chore(deps): bump epoch to d94f215 for FetchSnapshotConfig 1MB cap fix#4
Merged
tonicmuroq merged 1 commit intomainfrom May 6, 2026
Merged
Conversation
Picks up cocoonstack/epoch#3, which raises the snapshot-config blob read cap from 1 MiB to 64 MiB. Wake-side parse failed with "unexpected end of JSON input" when the SnapshotConfig — including per-file SparseMap fields for memory-ranges and overlay.qcow2 — grew past 1 MiB, which a 4 GiB Windows guest with a Firebase-active agent hits routinely. No vk-cocoon source changes; just the go.mod / go.sum bump and a rebuild. Existing tests pass. Co-Authored-By: Claude Opus 4.7 (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
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.
Pulls in cocoonstack/epoch#3 — raises the snapshot-config blob read cap from 1 MiB to 64 MiB so wake from a hibernate snapshot whose aggregated per-file sparse maps exceed 1 MiB no longer fails with
parse snapshot config: unexpected end of JSON input.Live repro: a 4 GiB Windows VM with a Firebase-active agent produces a 1.37 MB config blob (memory-ranges sparse map 580 KB + overlay.qcow2 sparse map 612 KB + base fields). Wake stays in vk-cocoon's UpdatePod retry loop indefinitely until this dep bump lands and vk-cocoon is redeployed.
No source changes here; just go.mod + go.sum + go build/test green.
🤖 Generated with Claude Code