fix(node): count event bytes correctly so the size limits are enforced - #1390
Open
sarmah-rup wants to merge 1 commit into
Open
fix(node): count event bytes correctly so the size limits are enforced#1390sarmah-rup wants to merge 1 commit into
sarmah-rup wants to merge 1 commit into
Conversation
✅ TVS Validation PassedShow detailsAll validation checks have successfully completed. |
🦋 Changeset detectedLatest commit: a876f56 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
What I hit
Sending server-side events with
@segment/analytics-node, oversized events weren't being caught by the client's size guard, so they'd ship and the API would reject the whole batch. It turned out the 32 KB per-event and 480 KB batch limits were not being enforced at all.Root cause
ContextBatch.calculateSize(packages/node/src/plugins/segmentio/context-batch.ts) is a broken copy of the well-known "count UTF-8 bytes" idiomencodeURI(str).split(/%..|./).length - 1:The
.(match any character) was mistyped as a literali, and the trailing- 1was dropped. So instead of counting bytes it counts%XXescapes plus the letter "i". A ~39 KB event measures as ~21, passes the 32 KB guard, and gets sent. This has been the case since batching was added in #640.Fix
Restore the correct byte count:
After the fix,
calculateSizeequalsBuffer.byteLength(json, 'utf8')across ASCII, multibyte, and URL-reserved inputs.Test
Added
packages/node/src/plugins/segmentio/__tests__/context-batch.test.ts: a ~39 KB event is now rejected ("Event exceeds maximum event size of 32 KB"), a small event is still accepted. Verified fail before / pass after (revert the regex and the size test fails). The existing 500 KB test is unaffected. Included apatchchangeset for@segment/analytics-node.