Loading debian/changelog +17 −0 Original line number Diff line number Diff line libnetplus (20260505+11) unstable; urgency=medium * QUIC: fix stream resurrection on retransmitted packets — when both sides completed a stream (send_fin + recv_fin), the stream was erased from _streams. Retransmitted packets for that stream then auto-created a new default Stream object, resetting recv_ranges to empty and recv_frame_count to 0. This caused: (a) _data_recv double-counting despite the +9 overlap fix (empty recv_ranges → overlap=0 → full retransmitted data counted as new unique bytes), (b) _peer_streams_bidi_opened inflation, (c) potential re-dispatch of stale data to the application callback, and (d) repeated "[QUIC-DIAG] HEAD frame: frame_count=1" log spam. Fix: track closed stream IDs in _closed_streams set; ignore STREAM frames for streams in that set. -- Jan Koester <jan.koester@tuxist.de> Mon, 05 May 2026 15:00:00 +0200 libnetplus (20260505+10) unstable; urgency=medium * QUIC: fix FIN-only STREAM frame never sent on the wire — when Loading Loading
debian/changelog +17 −0 Original line number Diff line number Diff line libnetplus (20260505+11) unstable; urgency=medium * QUIC: fix stream resurrection on retransmitted packets — when both sides completed a stream (send_fin + recv_fin), the stream was erased from _streams. Retransmitted packets for that stream then auto-created a new default Stream object, resetting recv_ranges to empty and recv_frame_count to 0. This caused: (a) _data_recv double-counting despite the +9 overlap fix (empty recv_ranges → overlap=0 → full retransmitted data counted as new unique bytes), (b) _peer_streams_bidi_opened inflation, (c) potential re-dispatch of stale data to the application callback, and (d) repeated "[QUIC-DIAG] HEAD frame: frame_count=1" log spam. Fix: track closed stream IDs in _closed_streams set; ignore STREAM frames for streams in that set. -- Jan Koester <jan.koester@tuxist.de> Mon, 05 May 2026 15:00:00 +0200 libnetplus (20260505+10) unstable; urgency=medium * QUIC: fix FIN-only STREAM frame never sent on the wire — when Loading