Files
proton-drive-linux/docs
nvrl cd90c566cd fix(fuse,core): renames across folders, replaced files, and writes after a create
Found by the seeded simulation runs (docs/BUGS.md).

- B122: a rename across folders goes to Drive as one move-multiple
  request, so a sibling holding the new name in the old folder no longer
  fails it with EIO. The drain uses the same request.
- B123: a second write open on a file just written no longer fails with
  EIO. An empty file counts as complete, our own renames, moves and
  online creates record their echo, a duplicated event is skipped, a
  rename keeps the file's mtime while its revision stays, and a landed
  upload is cached before open handles are rebased onto it.
- B124: a node put back after a failed replacing rename leaves `hidden`
  and its folder is listed again, so it shows in the mount.
- B131: a landed create is read back with the same short retry as an
  online create, and its bytes are cached under the real uid before an
  open handle is repointed at it.
- B135: an online rename settles the tree through the state guard, so
  the database has both folders unlisted before the reply. A lookup
  right after it no longer rebuilds the destination without the file.

The simulation runs no longer tolerate B122 or B131.
2026-10-03 14:50:12 +02:00
..
2026-10-01 21:39:05 +02:00

Documentation

For users

Page What it covers
Installation Packages, building from source, first sign-in, updating and uninstalling
User guide My files, available offline, synced folders, conflicts, Photos, sharing, Trash and versions, Computers, the search launcher, the tray
Command-line reference Every pdfs command, grouped by task, and scripting with --json
Configuration config.json, environment variables, file locations, the systemd service
Troubleshooting Diagnosing problems, common symptoms, starting over, reporting a bug
Recovering on a new computer What survives a lost machine and how to restore your synced folders
Changelog What changed in each release

For contributors

Page What it covers
Development guide Building, running and debugging from source; releasing
Architecture Crates, read and write paths, sync engine, control protocol, threads, threat model
Testing Unit tests and the FUSE acceptance suite
Translating Adding and updating translations
Roadmap Planned work and verification still owed
Bug ledger Every tracked defect with its analysis and status
UI/UX plan Design audit and notes behind the 2.x desktop app

Also see CONTRIBUTING.md and SECURITY.md in the repository root.