Skip to content

THRIFT-5848: Expose InputBufferUnderrunError in nodejs client#3097

Merged
Jens-G merged 1 commit intoapache:masterfrom
graphcore:expose-input-buffer-underrun-error
Feb 8, 2025
Merged

THRIFT-5848: Expose InputBufferUnderrunError in nodejs client#3097
Jens-G merged 1 commit intoapache:masterfrom
graphcore:expose-input-buffer-underrun-error

Conversation

@cameron-martin
Copy link
Contributor

Client: nodejs

When implementing a custom Connection, it is very useful to be able to respond to InputBufferUnderrunError to roll back the position of the transport. This is now exposed through the root module, so that custom connections can use this.

  • Did you create an Apache Jira ticket? (Request account here, not required for trivial changes)
  • If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
  • Did you squash your changes to a single commit? (not required, but preferred)
  • Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"?
  • If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

When implementing a custom `Connection`, it is very useful to be able to respond to `InputBufferUnderrunError` to roll back the position of the transport. This is now exposed through the root module, so that custom connections can use this.
@Jens-G Jens-G added the nodejs label Feb 5, 2025
@Jens-G Jens-G merged commit 7fe4bf5 into apache:master Feb 8, 2025
20 of 23 checks passed
@cameron-martin cameron-martin deleted the expose-input-buffer-underrun-error branch February 10, 2025 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants