Skip to content

fix: keep recv DATA FIFO to avoid sendToSonny index error - #50

Merged
esrrhs merged 1 commit into
masterfrom
fix/recvframe-data-order
Sep 24, 2026
Merged

esrrhs merged 1 commit into
masterfrom
fix/recvframe-data-order

Conversation

@esrrhs

@esrrhs esrrhs commented Sep 24, 2026

Copy link
Copy Markdown
Owner

Summary

  • Revert the v0.14.0 RecvFrame optimization that promoted DATA payloads <= 4096 bytes to prioInter.
  • Small chunks of the same TCP stream were jumping ahead of bulk frames, breaking per-sonny Index order and killing connections with sendToSonny index error.
  • Bump version to 0.14.1. SOCKS5 UDP associate and send-side interactive priority are unchanged.

Test plan

  • go test ./proxy
  • Fetch a large HTTPS page (e.g. https://www.google.com/) repeatedly over SOCKS5/rudp and confirm no sendToSonny index error
  • Confirm small requests still work (/generate_204, short redirects)

Made with Cursor

Small DATA was jumping ahead of bulk chunks of the same TCP stream, which breaks per-sonny Index order.

Co-authored-by: Cursor <[email protected]>
@esrrhs
esrrhs merged commit e1391f7 into master Sep 24, 2026
8 checks passed
@esrrhs
esrrhs deleted the fix/recvframe-data-order branch September 24, 2026 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant