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
Ship PR 940 (secretary invitations, long ask_user buttons, readable receipt) once Stage QA works, then verify the deployed revision #956
PR 940 (#940), head b711de1, has every hosted check green but its stage-qa status is 'error: not provisioned' because the Telegram login of the Stage QA browser host (65.21.40.51) is lost, tracked in #954. Remaining: owner login on the host, one Stage QA re-run on the exact head, rebase and re-bump the version if origin/main moved (the chat-serialization PR of session 615207 may land first), gh ship 940, the post-ship deploy and the exact-revision check on the odroid, then comments on #908, #909 and #526.
Why (motivation)
The fixes for the three incident problems (a question that never reached the user, a secretary who could not invite for the owner, an unreadable receipt after a partly failed run) are written, reviewed and hosted-CI green, but still not running in the live bot until this ships.
User impact
Until it ships, a secretary who asks the bot to invite people to the owner's event still gets a failed or invented-id reply, ask_user questions with long options still never reach people, and a partly failed request still ends in a list of attempts without event names.
Cost of inaction
The live bot keeps the three incident behaviours and the finished branch drifts from main and needs another rebase and review round.
Acceptance criteria
PR 940 is merged with a green stage-qa status on the exact head
The odroid runs the merge SHA (docker image tag, releases/current.json, /health and /ready) with no level>=50 log lines after the deploy
Comments with the merge SHA and verification are on issues 908, 909 and 526
Done: PR 940 merged as 4b2372d after Stage QA passed 6 cases on the exact head (run 41776088442), hosted CI green, hosted CI/CD deploy green; the odroid runs that revision (see the comments on 908, 909, 526). The post-ship runner recorded failed because of #959 (Cloudflare 403 for Python urllib), not because of the deployment.
Activity
alex-mextner commentedon Nov 4, 2026
Done: PR 940 merged as 4b2372d after Stage QA passed 6 cases on the exact head (run 41776088442), hosted CI green, hosted CI/CD deploy green; the odroid runs that revision (see the comments on 908, 909, 526). The post-ship runner recorded failed because of #959 (Cloudflare 403 for Python urllib), not because of the deployment.