fix: handling consistent cancellation across stream and locks #699
Conversation
This file contains 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
|
fenos
force-pushed
the
fix/handling-consistent-cancellation
branch
6 times, most recently
from
cf72ff1 to
4184c93
Compare
|
@Murderlon when you have sometime please have a test with this. |
fenos
force-pushed
the
fix/handling-consistent-cancellation
branch
from
4184c93 to
5291f62
Compare
Murderlon
approved these changes
Jan 18, 2025
Murderlon
added a commit
to netdown/tus-node-server
that referenced
this pull request
Jan 20, 2025
* main: (59 commits) Replace demo folder with StackBlitz (tus#704) @tus/gcs-store: correctly pass content type (tus#702) @tus/s3-store: fix zero byte files (tus#700) Update package-lock.json [ci] release (tus#696) fix: handling consistent cancellation across stream and locks (tus#699) @tus/s3-store: Change private modifier into protected (tus#698) Create funding-manifest-urls Bump @aws-sdk/client-s3 from 3.703.0 to 3.717.0 (tus#695) Bump mocha from 10.4.0 to 11.0.1 (tus#693) Bump @biomejs/biome from 1.9.2 to 1.9.4 (tus#694) [ci] release (tus#690) Bump @aws-sdk/client-s3 from 3.701.0 to 3.703.0 (tus#685) @tus/s3-store: fix part number increment (tus#689) Revert "Bump rimraf from 3.0.2 to 6.0.1 (tus#681)" Bump @aws-sdk/client-s3 from 3.682.0 to 3.701.0 (tus#683) Bump @changesets/cli from 2.27.9 to 2.27.10 (tus#682) Bump rimraf from 3.0.2 to 6.0.1 (tus#681) Bump @types/node from 20.11.5 to 22.10.1 (tus#679) Ignore JSON for Biome formatting ...
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.
This PR fixes #697 by always cancelling the context when the
req.on('close')is emitted.Handled Cancellation scenarios:
Client aborts the request (signal is propagated to the proxy stream and lockers)
Client completes the request correctly (without keep alive) the on('close') is still triggered, it will not have any effect but probably good practice to make sure all future resources are clean up.
Client completes the request correctly (with keep-alive) the on('close') is not triggered, context is still cancelled upon req.on('finish'), it will not have any effect but probably good practice to make sure all future resources are clean up.