aboutsummaryrefslogtreecommitdiff
path: root/.ai/sessions/2026-05-16-01-45-daily-prep-quick-reactive-and-github-cleanup.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-28 14:07:05 -0500
committerCraig Jennings <c@cjennings.net>2026-07-28 14:07:05 -0500
commitbff01385a17fd8435f202d70362db13a139774d6 (patch)
treea82a093cbfb2d9a389ab2f153abbab4204db3088 /.ai/sessions/2026-05-16-01-45-daily-prep-quick-reactive-and-github-cleanup.org
parent16756135ff2b70a47aded26e8ccf33dc249a9f17 (diff)
downloadrulesets-main.tar.gz
rulesets-main.zip
fix(triage): pass the TL object to loadChats, not a bare symbolHEADmain
Step 1 called (telega--loadChats 'main). That's a raw TL wrapper, so it drops its argument into the request as :chat_list untouched. The symbol went out on the wire as main, and the C parser aborts on any value it can't start. Every telegram sweep has been killing telega-server. Both call sites now pass '(:@type "chatListMain"), which is what telega's own callers use. I merged this with the down-is-launch fix parked since 2026-07-24 rather than applying either alone. The parked file still carried the bad call, and its new prose cited the segfault gotcha as the reason docker mode is mandatory. That's the same gotcha this rewrites to say the deaths were our own bad argument. Shipping them in sequence would have left the file arguing against itself, so I reconciled the prose in both places and kept the docker requirement on its own evidence. The gotcha keeps two caveats. A crash with no triage verb running needs its own investigation. And a short chat list is a real short list, because 19 was the true account size measured at both ends, not a scan truncated by this bug.
Diffstat (limited to '.ai/sessions/2026-05-16-01-45-daily-prep-quick-reactive-and-github-cleanup.org')
0 files changed, 0 insertions, 0 deletions