Browse Source
Go's fitTtlCount always converts to seconds first, then finds the coarsest unit that fits in one byte (e.g., 120m → 2h). Rust had an early return for count<=255 that skipped normalization, producing different binary encodings for the same duration.rust-volume-server
1 changed files with 4 additions and 8 deletions
Loading…
Reference in new issue