ZaStoGram_desktop/Telegram/SourceFiles/mtproto/runtime
Repository files (latest commit first)
Filename Latest commit message Latest commit date
loop-uh fb0c74e0d4 Report what the socket saw when no ServerHello came
A stall reported as zero received bytes is two different failures wearing
one face: an answer that never arrived, and an answer that arrived and was
never handed to this process. Nothing in the report told them apart, so
every round of this has ended in argument rather than measurement. The
relay side is now excluded by experiment - the client's own hello bytes,
rebuilt from client_hello_rules.cpp and sent from two networks, come back
with a verified ServerHello in twenty milliseconds while the client on the
same machine at the same moment gets nothing - so the next question is
strictly local, and these are the three facts that answer it.

sock_state is the socket's own state at the deadline, sock_avail its unread
backlog, rx_notify how many times it announced something to read. All three
appear only for the case in question: hello written, nothing received.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-26 15:40:17 +03:00
..
connection_status.cpp распил 2026-07-08 00:44:27 +03:00
connection_status.h fix 2026-07-08 16:28:12 +03:00
connection_status_types.h Name the camouflage answer instead of blaming the digest 2026-07-26 00:15:27 +03:00
proxy_data.h fix 2026-07-08 16:28:12 +03:00
proxy_endpoint.h Name the camouflage answer instead of blaming the digest 2026-07-26 00:15:27 +03:00
runtime_environment.cpp Report what the socket saw when no ServerHello came 2026-07-26 15:40:17 +03:00
runtime_environment.h Record that a server told us the time, not that it moved the clock 2026-07-26 14:08:52 +03:00