Repository navigation
Conversation
fix(db): sanitize NUL escapes in chat context snapshots
cskwork
added a commit
that referenced
this pull request
Nov 9, 2026
fix: promote chat context NUL sanitization to main
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.
Promote #80 from
devtomain. Chat context snapshots now use the existing JSONB sanitizer so captured NUL bytes cannot trigger PostgreSQL22P05or keep successful checkpoints pending for retry. No schema, public API, or user-facing text changes.Validation:
22P05; 24 focused tests/subtests passed after the fix on isolated native PostgreSQL, with no failures or skips.devcommitc0269c8f4918566daa9e428e461e11213ebb8cecbefore opening this promotion: checks, E2E.Merge with a merge commit to preserve
devancestry, then verify post-promotion CI and E2E.