feat(captp): handle send
rejections
#2427
Merged
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.
Closes: #2412
Description
Have CapTP abort the connection if
send
returns a promise rejection. The existing implementation only aborted ifsend
threw a synchronous exception.Security Considerations
Crisper handling of async transport-layer failures.
Scaling Considerations
n/a
Documentation Considerations
Allows effective use of
async
CapTP send functions.Testing Considerations
Usual CI.
Compatibility Considerations
Will abort the connection if an
async
send
rejects. Before, the rejection was ignored.Upgrade Considerations
n/a