| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| caprock_0.49.3_windows_amd64.zip | 2026-09-02 | 8.8 MB | |
| caprock_0.49.3_windows_arm64.zip | 2026-09-02 | 8.1 MB | |
| checksums.txt | 2026-09-02 | 600 Bytes | |
| caprock_0.49.3_darwin_amd64.tar.gz | 2026-09-02 | 8.8 MB | |
| caprock_0.49.3_darwin_arm64.tar.gz | 2026-09-02 | 8.3 MB | |
| caprock_0.49.3_linux_amd64.tar.gz | 2026-09-02 | 8.7 MB | |
| caprock_0.49.3_linux_arm64.tar.gz | 2026-09-02 | 8.1 MB | |
| README.md | 2026-09-02 | 974 Bytes | |
| v0.49.3 source code.tar.gz | 2026-09-02 | 6.2 MB | |
| v0.49.3 source code.zip | 2026-09-02 | 6.5 MB | |
| Totals: 10 Items | 63.5 MB | 0 | |
Fixed
-
"Burn now" says it is measuring instead of extrapolating. 0.49.1 made the rate divide by the time it actually covers, which is correct arithmetic and an alarming number: a daemon twenty seconds old showed $3,215/h, because twenty seconds of a busy minute extrapolates to that. Until the window has been lived through, the tile shows a dash and says it needs ten minutes of running — a figure nobody can act on is worse than no figure.
-
A test that asserted a promise the code never made. One of the night's new tests demanded that a healthy terminal subscriber receive 300 of 400 chunks while another subscriber sat stalled. The buffer is deliberately lossy — a reader that falls behind legitimately misses some — so the test passed on a fast machine and failed in CI, which is what stopped v0.49.2 from publishing. It asserts what the code actually promises now: the writer finishes and a healthy reader keeps receiving.