nvrl 307305282e fix(fuse,core): what a create sent, and where, outlives a restart and a rename (B182, B183, B184) ...

The known-bug confirmation run failed one_client_on_a_flaky_link seeds 6
and 11 on three bugs around a create whose answer was lost:

- B182: after a restart, a write over a file whose create landed but was
  never read back forked a conflict copy. A revision of a file that has
  no revision of Drive's now adopts the landed node first.
- B183: the SHA-1s a create sent were kept in memory, so after a restart
  its trash or retry no longer knew the node Drive made. They are now on
  the op's row (pending_op.sent_sha1, schema 42).
- B184: a rename rewrote the op's target, and the trash and the retry
  looked for the node under the last name only. Each attempt's parent
  and name are recorded (pending_op.sent_to); the trash looks under all
  of them, and a retry adopts the node an earlier attempt made and moves
  it to the current name.

2026-10-05 02:01:50 +02:00

..

pdfs-cli

feat(core,fuse,gui): show a sync issue on its node in the file browser

2026-10-05 01:06:03 +02:00

pdfs-core

fix(fuse,core): what a create sent, and where, outlives a restart and a rename (B182, B183, B184)

2026-10-05 02:01:50 +02:00

pdfs-fuse

fix(fuse,core): what a create sent, and where, outlives a restart and a rename (B182, B183, B184)

2026-10-05 02:01:50 +02:00

pdfs-gui

feat(core,fuse,gui): show a sync issue on its node in the file browser

2026-10-05 01:06:03 +02:00