ospab 39127d30f3 §B: fix Closing-state teardown data loss (from 47d44fa) ... In the Closing state the old code force-transitioned to Closed after a SINGLE inbound packet, so any data/ACKs the peer still had in flight when we initiated Close were dropped (Closed returns Noop for everything). Stay in Closing and process inbound normally; handle_inbound already owns the Close->Closed transition when it actually receives the peer's Close frame. Also handle Tick in Closing so our own Close frame is retransmitted until acknowledged. Ported surgically from 47d44fa — only the Closing-state correctness fix, NOT that commit's bundled RFC-6298 RTO / congestion rewrite (a behavioural change to the working base) or the sent_history BTreeMap perf swap (broad hot-path change for a perf-only gain). cargo test -p ostp-core: 36/36 incl. test_close_sequence. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-28 01:44:37 +03:00
..
src	§B: fix Closing-state teardown data loss (from 47d44fa)	2026-06-28 01:44:37 +03:00
Cargo.toml	feat: implement custom Reality protocol with ChaCha20Poly1305 and X25519	2026-05-29 15:00:17 +03:00