mirror of
https://github.com/narrrl/proton-drive-linux.git
synced 2026-11-07 01:12:10 +01:00
nvrl
3f74b95b34
B154 is a regression from the B153 fix: after a failure on a held name the op woke the ops waiting for it, but the database cannot see a create on the wire, so the op was due again at once and spent its waits in milliseconds. No wake while another create on the wire holds the name. B155: a revision upload that reached Drive but lost its answer left the file at a revision this daemon never heard of, and the retry kept the write as a conflict copy of itself. A complete write whose bytes the remote holds, by size and SHA-1, is sent again instead. The fake Drive gains hold_reply_to_next_create and lose_reply_to_next_revision for the two new sim tests.
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.