Conversation
The continuous replication section was named plus.litestream in code, with disaster_recovery only as a serde alias, while the docs named plus.disaster_recovery. Rename the type and field to the documented key and drop the alias. Also drop the unused sftp replica scheme, so the section reads scheme: file | s3, and fix the docs example, which showed a replicas array the code never accepted.
Contributor
|
| Project | Bencher |
| Branch | u/ep/s3-r2/disaster-recovery |
| Testbed | intel-v1 |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result microseconds (µs) (Result Δ%) | Upper Boundary microseconds (µs) (Limit %) |
|---|---|---|---|
| Adapter::Json | 📈 view plot 🚷 view threshold | 5.18 µs(+7.21%)Baseline: 4.83 µs | 5.84 µs (88.70%) |
| Adapter::Magic (JSON) | 📈 view plot 🚷 view threshold | 4.96 µs(+5.94%)Baseline: 4.68 µs | 5.56 µs (89.16%) |
| Adapter::Magic (Rust) | 📈 view plot 🚷 view threshold | 27.50 µs(+4.38%)Baseline: 26.34 µs | 29.62 µs (92.83%) |
| Adapter::Rust | 📈 view plot 🚷 view threshold | 4.68 µs(+22.02%)Baseline: 3.84 µs | 5.90 µs (79.38%) |
| Adapter::RustBench | 📈 view plot 🚷 view threshold | 4.66 µs(+21.65%)Baseline: 3.83 µs | 5.88 µs (79.31%) |
epompeii
added this pull request to stack #1042
September 18, 2026 06:48
epompeii
marked this pull request as ready for review
September 18, 2026 06:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The continuous replication section of the server config was named
plus.litestreamin code, withdisaster_recoveryaccepted only as a serde alias, while the docs have always named itplus.disaster_recovery. This makes the documented key the only key, drops the unusedsftpreplica scheme, and fixes the docs example, which showed areplicasarray the code never accepted.Changes
JsonPlus.litestreambecomesdisaster_recovery: Option<JsonDisasterRecovery>; the alias is gone. The code that runs the Litestream binary keeps its Litestream names, since that is the vendor it drives.JsonReplica::Sftpand its YAML mapping are removed, so the section readsscheme: file | s3.sftpscheme; the shared config example shows a singlereplica.disaster_recoverydeserializes forfileands3, thatsftpis rejected, and that a leftoverlitestreamkey is ignored.Breaking changes
plus.litestreamis ignored and continuous replication does not start. Rename the key toplus.disaster_recovery.sftpreplica scheme is removed.fileands3remain.First of a stack of three: this, then removing the on demand backup endpoint, then moving the container registry storage onto
object_storewith the samescheme: file | s3config shape.