Skip to content

Document PDrive's upstream rclone work #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ClaudiuSchuster merged 1 commit into from
Aug 27, 2026
Merged

Document PDrive's upstream rclone work #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,12 +139,15 @@ git pull --ff-only

PDrive installs a pinned, checksum-verified rclone build published from its
public source fork. It contains the upstream fix for
[rclone #9722](https://github.com/rclone/rclone/issues/9722), a source-pinned API
bridge fix and a Proton file-data limiter that leaves metadata browsing outside
bulk transfer limits. The weekly updater stays on that reviewed PDrive build
until this project publishes a replacement and never restarts an active mount.
The optional official Proton Drive CLI is a separate client and is not required
by this project.
[rclone #9722](https://github.com/rclone/rclone/issues/9722), the API bridge
worker fix proposed in
[Proton-API-Bridge #8](https://github.com/rclone/Proton-API-Bridge/pull/8) and the
Proton file-data limiter tracked in
[rclone #9832](https://github.com/rclone/rclone/issues/9832). The limiter leaves
metadata browsing outside bulk transfer limits. The weekly updater stays on
that reviewed PDrive build until this project publishes a replacement and never
restarts an active mount. The optional official Proton Drive CLI is a separate
client and is not required by this project.

## Uninstall

Expand Down
5 changes: 5 additions & 0 deletions docs/DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,11 @@ The installed binary comes from the public
[`oss-singularity/Proton-API-Bridge`](https://github.com/oss-singularity/Proton-API-Bridge)
commit used to build the asset; the bridge worker-drain correction is proposed
upstream in [Proton-API-Bridge PR #8](https://github.com/rclone/Proton-API-Bridge/pull/8).
The independent Proton file-data limiter, its reproduction measurements and the
public prototype are tracked in
[rclone issue #9832](https://github.com/rclone/rclone/issues/9832). Keep these
upstream efforts separate: one fixes leaked upload-worker slots after errors;
the other limits only bulk file readers so API metadata remains responsive.
The Linux x86-64 asset is statically linked and its checksum is embedded in
`pdrive-prerequisites` and published beside the release.

Expand Down
9 changes: 6 additions & 3 deletions docs/OPERATIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -838,9 +838,12 @@ rclone release. `pdrive-prerequisites` verifies the embedded SHA-256 digest,
minimum upload-safe version and required Proton backend command before atomic
installation. The updater invokes that same verifier and does not follow
rclone's official stable channel, because an otherwise newer binary may lack
PDrive's source-reviewed file-data limiter and bridge-worker fix. A newly
installed binary is intentionally left for the next natural mount start; the
updater never restarts an active transfer.
PDrive's source-reviewed file-data limiter and bridge-worker fix. Their upstream
review is tracked independently in
[rclone #9832](https://github.com/rclone/rclone/issues/9832) and
[Proton-API-Bridge #8](https://github.com/rclone/Proton-API-Bridge/pull/8).
A newly installed binary is intentionally left for the next natural mount
start; the updater never restarts an active transfer.

The optional official Proton Drive CLI timer runs five minutes after boot when
due and daily with up to four hours of randomized delay. Its updater accepts
Expand Down
9 changes: 6 additions & 3 deletions docs/TROUBLESHOOTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -397,9 +397,12 @@ The upstream correction is tracked in
[rclone #9722](https://github.com/rclone/rclone/issues/9722). New toolkit
installations use a pinned, checksum-verified PDrive rclone build based on the
fixed beta. Its source also pins the API bridge worker-drain correction and adds
the file-data-only limiter. The weekly updater keeps this reviewed build until
PDrive publishes a replacement instead of replacing it with an incompatible
official binary.
the file-data-only limiter. The bridge correction is proposed upstream in
[Proton-API-Bridge #8](https://github.com/rclone/Proton-API-Bridge/pull/8), while
the limiter's measurements and proposed backend contract are tracked in
[rclone #9832](https://github.com/rclone/rclone/issues/9832). The weekly updater
keeps this reviewed build until PDrive publishes a replacement instead of
replacing it with an incompatible official binary.

The guarded helper does not treat an ordinary 100% transfer as stalled. It
requires a terminal backend error in the completion window, a fixed rclone,
Expand Down