THRIFT-4564: Correctly reset the transport in NodeJS - #3919
Open
KarboniteKream wants to merge 2 commits into
Open
KarboniteKream wants to merge 2 commits into
KarboniteKream wants to merge 2 commits into
Conversation
Member
Code reviewNo blocking issues found. Checked for bugs and CLAUDE.md compliance. Two suggestions, below the bar for an issue but verified:
Lines 22 to 27 in e8b37a0
thrift/compiler/cpp/src/thrift/generate/t_js_generator.cc Lines 2277 to 2281 in e8b37a0 thrift/lib/nodejs/lib/thrift/buffered_transport.js Lines 39 to 47 in e8b37a0 🤖 Generated with Claude Code |
Client: nodejs
KarboniteKream
force-pushed
the
fix/nodejs-transport-reset
branch
from
September 22, 2026 03:03
e8b37a0 to
e9d233f
Compare
This branch has not been deployed
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.
Client: nodejs
Jira: THRIFT-4564
This PR is a follow-up to #1558, where the
reset()method was added toTBufferedTransport. I discovered that the code was trying to callreset()on the protocol in the NodeJS branch, instead of on the transport, as intended. The missing.getTransport()was added, with an appropriate test.The
reset()method is also added toTFramedTransport, to unify the behavior.