You'll notice
Useful2 Signal2
Shared memory sync adopts an identical remote file instead of erroring on the collision.
What's wrong with this entry?
Anonymous. No account, no email.
What
When syncing shared memory files, a create that collides with an existing remote path now re-reads that file: if its contents hash matches what was about to be uploaded, the existing file is adopted and the collision is logged rather than treated as an error.
Details
- Creates now declare that the path must not already exist, making the collision explicit.
- A collision where the contents differ still raises the error.
- Update failures caused by a stale file id are rechecked by re-reading the file rather than by a bare existence probe.
Evidence
multi-store-sync[
Strings lifted out of the shipped bundle, so the claim above can be checked against them.