When a client creates new automerge documents and syncs them to a samod server that uses DontAnnounce announce policy, the documents are silently lost. A fresh client reconnecting to the same server will get Document <id> is unavailable for every document the first client created.
The bug is deterministic and affects every document synced to the server.
We encountered this through our javascript frontend, but we also have a pure Rust repro at https://github.com/cscheid/samod-repro (this is based on the 0.7.1 release we were working off, but the issue persists on main).
Posting a fix for this in a PR.
When a client creates new automerge documents and syncs them to a samod server that uses
DontAnnounceannounce policy, the documents are silently lost. A fresh client reconnecting to the same server will getDocument <id> is unavailablefor every document the first client created.The bug is deterministic and affects every document synced to the server.
We encountered this through our javascript frontend, but we also have a pure Rust repro at https://github.com/cscheid/samod-repro (this is based on the 0.7.1 release we were working off, but the issue persists on main).
Posting a fix for this in a PR.