Repository navigation
fix(seq): write context values as raw JSON only when they are valid JSON literals - #6
Merged
Merged
Conversation
mxmgorin
force-pushed
the
fix/seq-context-json-literals
branch
from
October 21, 2026 12:17
505b930 to
7e2563c
Compare
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.
Context values that looked numeric to
my_json::json_utils::is_numberwere written unquoted, including values that are not valid JSON numbers (0922). Seq rejects such a payload with 400 and drops the whole chunk;NULL/Truehad the same problem.Seq ingestion log:
null/true/false(case-sensitive). Everything else is written as a string.