Repository navigation
refactor(value): Preserve known UTF-8 as strings - #26608
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 626c987b44
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Keeps statically known UTF-8 values in Value::String. Updates source metadata, formatted values, and affected test expectations.
626c987 to
0a6b440
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0a6b440d90
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
gwenaskell
left a comment
There was a problem hiding this comment.
nice! just one suggestion below
When truncating the `message` field of a log event, the `datadog_logs` converts it into a string, chops part of it off, adds a truncation marker string, but then stuffs it back into the event as a `Bytes` value. Since we know it is valid UTF-8 by construction, we can use the `String` type instead. This was previously submitted as part of #26608. While it looks like a bug fix, the extra boundary check is not actually reachable in the current caller and so is purely defensive against future (mis)uses.
Summary
Keeps statically known UTF-8 values in
Value::String. Updates source metadata, formatted values, and affected test expectations.References
Vector configuration
How did you test this PR?
Does this PR include user facing changes?
no-changeloglabel to this PR.Contributor Guidelines
@vectordotdev/vectorto reach out to us regarding this PR.git merge origin masterandgit push.