You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
KiteTicker connection drop is not detected due to non-functional ping loop (_loop_ping does not send pings) #237
In kiteconnect/ticker.py, the _loop_ping method is scheduled during onOpen to maintain connection health. However, the method only updates _last_ping_time and schedules the next call; it never actually transmits a ping frame (self.sendPing() is never called).
Because of this, self._last_pong_time remains None indefinitely, rendering the _loop_pong_check connection drop detector inactive. In the event of a silent network drop (e.g., losing internet/WiFi without a TCP reset), the socket remains in a "ghost" connected state until the OS TCP keepalive timeout (which defaults to 2 hours on macOS) kills it.
Activity
AnkitaAdvitot commentedon Sep 17, 2026
I have submitted a fix for this in #245 with full unit test coverage.