nvrl 4676a4e32b fix(fuse): cache an upload whose read-back failed, and know it as ours (B157) ...

When the read-back after an upload went unanswered, the drain let go of
the staged blob without caching it. A partial write opened next had
nothing to fill its gaps from and queued an incomplete revision, so the
write open after it was refused with EIO.

The bytes are now cached under the size and mtime the tree still has,
which is the base the next write takes. Their SHA-1 stands in for the
revision id the read-back did not bring, so that write chains onto the
upload and does not fork a conflict copy of itself.

2026-10-04 16:20:54 +02:00

..

pdfs-cli

feat(core,fuse,cli,gui): report changes Drive refuses as sync issues

2026-10-04 03:18:57 +02:00

pdfs-core

fix(core,fuse): a node written under its stand-in after landing updates its landed row

2026-10-04 13:38:54 +02:00

pdfs-fuse

fix(fuse): cache an upload whose read-back failed, and know it as ours (B157)

2026-10-04 16:20:54 +02:00

pdfs-gui

feat(core,fuse,cli,gui): report changes Drive refuses as sync issues

2026-10-04 03:18:57 +02:00