531 Kick answered 429 Too Many Requests warnings in the current moho.log, in bursts of about fifteen at each reconnect. The retry in socket.rs recovers every channel, so nothing goes missing - but a reconnect takes longer than it should and the log is mostly this.
Connecting at three at a time is still too fast for an account with this many channels after a reconnect (the comment above CONNECT_CONCURRENCY says four; the constant is three). Pace it by what Kick's 429 says - a Retry-After or a backoff shared by the whole batch - rather than each channel retrying on its own clock.
531 `Kick answered 429 Too Many Requests` warnings in the current moho.log, in bursts of about fifteen at each reconnect. The retry in socket.rs recovers every channel, so nothing goes missing - but a reconnect takes longer than it should and the log is mostly this.
Connecting at three at a time is still too fast for an account with this many channels after a reconnect (the comment above CONNECT_CONCURRENCY says four; the constant is three). Pace it by what Kick's 429 says - a Retry-After or a backoff shared by the whole batch - rather than each channel retrying on its own clock.
Salastil
added this to the v1.0 milestone 2026-10-01 23:59:58 -04:00
Fixed in code, waiting on a live check before closing.
A reconnect now resubscribes channels it already knows without asking Kick, and only fetches one page of history each; the connect-time requests share one pause on a 429. Tested against a local server that answers 429; not yet seen against Kick. To confirm: after moho restarts on this build, a reconnect should log no 'Kick answered 429' lines.
Fixed in code, waiting on a live check before closing.
A reconnect now resubscribes channels it already knows without asking Kick, and only fetches one page of history each; the connect-time requests share one pause on a 429. Tested against a local server that answers 429; not yet seen against Kick. To confirm: after moho restarts on this build, a reconnect should log no 'Kick answered 429' lines.
https://git.salastil.com/Salastil/nobilis/commit/f592a22a16e3593bf104b9c99221af38320d2657
https://git.salastil.com/Salastil/moho/commit/34ade1aa8a17ff4d3ff80224c74287cf42772617
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
531
Kick answered 429 Too Many Requestswarnings in the current moho.log, in bursts of about fifteen at each reconnect. The retry in socket.rs recovers every channel, so nothing goes missing - but a reconnect takes longer than it should and the log is mostly this.Connecting at three at a time is still too fast for an account with this many channels after a reconnect (the comment above CONNECT_CONCURRENCY says four; the constant is three). Pace it by what Kick's 429 says - a Retry-After or a backoff shared by the whole batch - rather than each channel retrying on its own clock.
Fixed in code, waiting on a live check before closing.
A reconnect now resubscribes channels it already knows without asking Kick, and only fetches one page of history each; the connect-time requests share one pause on a 429. Tested against a local server that answers 429; not yet seen against Kick. To confirm: after moho restarts on this build, a reconnect should log no 'Kick answered 429' lines.
f592a22a1634ade1aa8aFinished
f592a22a16c99d52be61c2e40dd5b62732d0868534ade1aa8a338095642c6fcc83a9b3