SftpReadStream: fall back to the storage's own stream instead of failing a read

2026-10-09 11:24:37 +02:00
parent c775e27dd2
commit b3e3054737
4 changed files with 440 additions and 54 deletions
@@ -18,7 +18,10 @@ instead carried by the app description, the git tag, the release, and this file.
 - Reading from an SFTP location waited a full round trip for every 256 KiB, whatever the line
  speed. Reads now keep up to 8 requests in flight. Restoring 1.97 GB in 500 files from a Hetzner
  Storage Box (47 ms away) took 694 s before the fix above, 499 s with it and 142 s with both
-  (2.8 → 3.9 → 13.9 MB/s); a full 51 GB restore ran at 13.0 MB/s.
+  (2.8 → 3.9 → 13.9 MB/s); a full 51 GB restore ran at 13.0 MB/s. When a server error
+  interrupts such a read, it goes on from the same position with Nextcloud's own SFTP stream;
+  after three failing files in a row, or on a Nextcloud whose SFTP library lacks what this needs,
+  only Nextcloud's own stream is used.
 - README: a WebDAV location on a slow upload needs a higher `davstorage.request_timeout`.

 ## [0.9.3-beta.4] - 2026-10-08