Truncate logs based on utf bytes instead of characters. #938
Conversation
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
…arantee each character is exactly 2 bytes, so our previous truncation logic did not work for large messages containing a lot of unicode characters. Although @google-cloud/logging-winston uses the default maxEntrySize of 250k, when all of those characters are in a single json field, it was still not truncating.
kmandrika
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There's no guarantee each character is exactly 2 bytes, so our previous truncation logic did not work for large messages containing a lot of unicode characters.
Although @google-cloud/logging-winston uses the default maxEntrySize of 250k, when all of those characters are in a single json field, it was still not truncating.
Checklist (if applicable):