Uh oh!
There was an error while loading. Please reload this page.
fix(cache): recover unreadable cache rows - #555
Closed
wan9chi wants to merge 1 commit into
Closed
Conversation
wan9chi
commented
Jul 21, 2026
MemberAuthor
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jul 21, 2026
Co-authored-by: GPT-5.6 Codex <codex@openai.com>
wan9chiforce-pushed
the
agent/cache-row-recovery
branch
from
July 21, 2026 03:56
a159706 to
ffed460Comparewan9chiforce-pushed
the
agent/cache-preallocation-limit
branch
from
July 21, 2026 03:56
02a2fad to
c682426Compare
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 freeto 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.

Motivation
A malformed or incompatible value in the local SQLite cache should not prevent a task from running. Decode failures currently escape cache lookup as fatal errors, and a stale fingerprint can continue pointing at a missing cache entry.
Changes