blob: 7c54ede7b7645e99d16611f31698310371c37f6f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
Fix for a defect in triage-intake.telegram.org: the numbered Step 1 was missing the mandatory `(setq telega-use-docker t)` that the plugin's own Quick Reference and SEGFAULT gotcha both require. Attached is the edited workflow file (.ai/workflows/triage-intake.telegram.org) — please take it into the canonical at claude-templates/.ai/workflows/.
THE DEFECT
The plugin contradicts itself across three places:
- Quick Reference (line 35): `emacsclient -e "(progn (setq telega-use-docker t) (telega t) 'started)"` — has the setq.
- SEGFAULT gotcha (line ~170): "docker mode stays mandatory (telega-use-docker = t; the setq before (telega t) is still the right defense)".
- Numbered Step 1 (lines 91-93): `(progn (unless (...live-p) (telega t)) 'started)` — NO setq.
telega-use-docker defaults to nil. In native (non-docker) mode the dockerized-vs-native tdlib difference is exactly the SEGFAULT the gotcha documents (exit 139). A session following the numbered Step 1 literally, on a daemon where nothing had already forced telega-use-docker to t, starts telega native and crashes the server — which the engine reports as SCAN FAILED at the top of the summary. Both of Craig's personal projects that use the telegram source (work and home) reported triage-intake failing.
THE FIX
Added `(setq telega-use-docker t)` as the first form in Step 1's progn, before the `(unless ... (telega t))`, with a comment pointing at the gotcha. Now Step 1 matches the Quick Reference. Minimal, wording/robustness only; no behavior change on a daemon that already had docker mode on.
IMPORTANT CAVEAT — this is a real defect but NOT a confirmed root cause. I could not reproduce the original failure: Craig doesn't remember the symptom ("it was much earlier"), and his .emacs.d daemon currently reads telega-use-docker t (via .emacs.d's telega-config `:custom`), so on his machine right now the missing setq may have been moot. The fix removes one genuine failure mode that matches the reported symptom; whether it was THE cause is unconfirmed. I've asked work and home for their actual error via their inboxes; if they come back with something else (e.g. the recent :TRIAGE_SOURCES: gating change 4d87f35, or a different source), I'll send a follow-up.
Two things worth your judgment on the canonical:
1. The stale note at line 37 ("Craig's daemon currently has telega-use-docker nil") is now false on .emacs.d — telega-config sets it t. Consider softening it to "the daemon's default is nil unless an Emacs-config :custom forces it," since the workflow syncs to machines/daemons without that config.
2. If the daemon reliably has docker mode on everywhere telega runs, this whole class is belt-and-braces — but Step 1 contradicting the Quick Reference is a defect regardless, and the belt is cheap.
No reply needed unless you disagree with the fix.
|
