Repository navigation
build: camex 4.0.1 in the tunnel, TCP fixed (2.24.3) - #282
Conversation
camex 4.0.1 (OpenIPC/camex#180) fixes the tunnel over TCP: a frame body read in pieces lost its first piece and server-to-client traffic stalled at about 10 KB/s. The client library had the bug as well, so the box needs this build. tests/e2e.sh takes TRANSPORT=TCP, checks the TCP connection to the hub and the video rate through tun0, and prints the tunnel's ping RTT. On the Docker network the RTT is a few ms and #180 does not show there (#281).
PR Summary by QodoUpgrade camex to 4.0.1 for the TCP tunnel fix
AI Description
Merge Risk
|
Code Review by Qodo
1. Rate check passes the buggy camex 4.0.0
|
|
Qodo review on 60c7428:
|
camex 4.0.1 (OpenIPC/camex#180, PR OpenIPC/camex#181) fixes the tunnel over TCP: a frame body read in pieces lost its first piece, so traffic from the server to the box stalled at about 10 KB/s. The bug was in the shared receive path, so the client library needs the fix too, not only the server. UDP is unaffected; no protocol or CLI changes.
bundles/camex→9e721e5(4.0.1); version 2.24.3 (versionCode 60), CHANGELOG, README (three languages) name camex 4.0.1.tests/e2e.sh:TRANSPORT=UDP|TCPfor the tunnel in Network; on TCP it checks the app's TCP connection to the hub; on both it checks the video rate throughtun0(100 KB/s or more) and prints the tunnel's ping RTT.docs/testing.md: 15 checks, 16 with TCP.The rate check does not catch #180 itself: the Docker network has a few ms of RTT and camex 4.0.0 passed it over TCP (874 KB/s). A real round trip in the test is #281.
Tests (local, Docker):
testDebugUnitTest lintDebug assembleDebugincompot/android:2026.10: pass.TRANSPORT=TCP tests/e2e.sh 34: 16 passed (904 KB/s);TRANSPORT=TCP tests/e2e.sh 21: 16 passed (892 KB/s);tests/e2e.sh 34(UDP): 15 passed (899 KB/s).After the release: the sberbox-1 tunnel to a 4.0.1 server switched to TCP (real RTT ~80 ms).