Skip to content

Acknowledge browser file streams - #317

Closed
skolarianer wants to merge 3 commits into
sol1:mainfrom
skolarianer:fix/client-file-stream-acks
Closed

skolarianer wants to merge 3 commits into
sol1:mainfrom
skolarianer:fix/client-file-stream-acks

Conversation

@skolarianer

@skolarianer skolarianer commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

The browser now acknowledges incoming file streams after constructing the BlobReader, then acknowledges each received blob from its progress callback. This keeps the client file stream's flow control moving as data arrives.

Adds a focused Node test for both acknowledgements.

Tested: git diff --check; node tests/client-file-stream-ack.mjs

May fixes #123 as suggested here: #284 (comment)

@skolarianer

Copy link
Copy Markdown
Contributor Author

One clarification: I understand issue #123 as describing uploads from the browser to the remote session's drive. This PR changes client.onfile, which handles files sent from the remote session to the browser, so issue #123 appears to describe the opposite transfer direction from this fix. Please correct me if I have misunderstood the stream path you had in mind.

@skolarianer
skolarianer force-pushed the fix/client-file-stream-acks branch from 7f9c494 to 6ccc6f3 Compare October 20, 2026 14:57
@davekempe

Copy link
Copy Markdown
Member

Merged in 1.13.3, thanks! Confirmed it on a live SSH session: a file sent from the session never reached the browser on 1.13.2, and with this it downloads straight away. You're right that it's the download direction, so it covers #123 item 4 but not the upload disconnect in item 1. #284 can come out of draft whenever you're ready.

@davekempe davekempe closed this Oct 21, 2026
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.

Drive feature unstable with uploads and downloads on Debian

2 participants