Claude 7da254fc45 Fix request_id mismatch causing 5s hang on every PUT commit
The COMMIT_PUT message was built with request_id N, then request_id
was incremented to N+1 immediately after sending. When the server
replied with request_id N, the client compared it against N+1,
silently discarded the reply, and waited for the 5-second timeout.
The timeout retry (replay_request) then resent with N+1, which
matched — so every PUT paid an unnecessary 5-second penalty.

Move the request_id++ before building the CommitPutMessage, matching
the pattern already used by toastyfs_async_delete.

https://claude.ai/code/session_01EG3WZSH3ZeTdAbb5T42r2w
2026-02-21 23:36:18 +00:00
2026-02-20 16:55:29 +01:00
2026-02-21 22:32:51 +00:00
2026-02-21 16:10:40 +01:00

ToastyFS

Turn your potato hardware into an extremely fault-tolerant object storage!

S
Description
A simple, fault-tolerant, highly available object storage
Readme MIT
1.1 MiB
Languages
C 98.4%
Shell 1%
Zig 0.4%
Batchfile 0.2%