Drain discovery responses before non-2xx errors#65
Merged
Conversation
dkropachev
force-pushed
the
dkropachev/driver-744-non200-connection-reuse
branch
from
June 30, 2026 03:34
b982002 to
6f466f2
Compare
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
1 participant
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.
Fixes #64
Drains discovery response bodies before throwing on non-2xx
/localnodesresponses so the Node HTTP handler can keep the socket reusable.Adds repeated non-2xx keep-alive connection reuse coverage for:
/localnodesdiscovery responsesListTablesresponses through the real Node client/request-handler pathBoth tests send multiple non-2xx responses before a success and assert all requests reuse the same accepted TCP connection.
Tests:
npm test -- --run test/discovery.test.tsnpm run typechecknpm run lint -- --quiet