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.
2026-05-13, Version 22.22.3 'Jod' (LTS), @marco-ippolito #63250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
2026-05-13, Version 22.22.3 'Jod' (LTS), @marco-ippolito #63250
Changes from 1 commit
1769d7412a246239147c12e91b28b9240bc9a2e2135065a0adb722725f9bb8e005508dd333f48f0dbe8171e5a5967c8b2cd358687d0c24a25e7db13e3d65c7a2df2d8a1799a4eae2c2792804cd22685671d1f445dcc60d50860971ec11f3c578a9a9daaead3d568a1b447fb9a89ad7dccf39566363f9a917c0a614a09efb3a27669b6957e157fb008977ef80785b00c79aa32cffda97ab8ddbc13ff8ffdd3394971a5cec0f49b51d22ff2d8bbcce09b819cb9ae5c16273cac05e742ab70226c8de4c0d992fdb5ce32831b5c2244503ea39ff9f45080ee02966ecfa76657c30354f78090f22ebdcaa2c1ec37c2fd602797dea64bdb5ad8f5182f1e5739fad6cec54652f4045c7670b8e6b8e209761855829491be801fc86fc6ec9a70d8075589b5797945b3506fdfa0ffFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
In TextEncoder.encodeInto, the destination buffer's byte length is read as a size_t but then implicitly narrowed to int when passed as the capacity argument to v8::String::WriteUtf8. When the destination view is larger than INT_MAX (2,147,483,647 bytes), the narrowing conversion underflows to a negative value, V8 treats it as "no capacity", and writes 0 bytes - returning { read: 0, written: 0 } even though the buffer has plenty of room. Clamp the capacity to INT_MAX before passing it to WriteUtf8. This is sufficient because the source string in encodeInto is bounded in practice and never requires more than INT_MAX bytes to encode; only the destination view length can exceed INT_MAX. This issue is already fixed on main and v24.x as a side effect of PR #58070, which migrated to the non-deprecated WriteUtf8V2 method whose capacity parameter is size_t. WriteUtf8V2 is not available in v22.x's V8 version, so this minimal patch fixes only the EncodeInto path instead of backporting the full migration. Refs: #58070 Fixes: #62610 Signed-off-by: semimikoh <ejffjeosms@gmail.com> PR-URL: #62621 Reviewed-By: René <contact.9a5d6388@renegade334.me.uk> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing