Skip to content

Comments

Resolve pull when read is successful#222

Merged
reillyeon merged 2 commits intomainfrom
resolve_pull
Feb 18, 2026
Merged

Resolve pull when read is successful#222
reillyeon merged 2 commits intomainfrom
resolve_pull

Conversation

@reillyeon
Copy link
Collaborator

It appears that the "Note" that immediately returning a resolved Promise is required to allow a stream to be cancelled while there is a pull() in progress was incorrect. The steps are updated to return a Promise that is resolved when the pull() succeeds.

Fixed #221.

It appears that the "Note" that immediately returning a resolved Promise
is required to allow a stream to be cancelled while there is a pull() in
progress was incorrect. The steps are updated to return a Promise that
is resolved when the pull() succeeds.

Fixed #221.
@reillyeon reillyeon requested a review from nondebug February 18, 2026 02:38
Copy link
Collaborator

@nondebug nondebug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@reillyeon reillyeon merged commit 11f6161 into main Feb 18, 2026
2 checks passed
@reillyeon reillyeon deleted the resolve_pull branch February 18, 2026 22:50
github-actions bot added a commit that referenced this pull request Feb 18, 2026
SHA: 11f6161
Reason: push, by reillyeon

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Should pullAlgorithm resolve when the pull actually finishes?

2 participants