Repository navigation
A friend chat sometimes jumps back to Chief's chat on its own (not reproduced) #261
Description
Seen on box instance A (main 7922771): after a while on a friend chat (e.g. "Helper · UiB1415's Bot") the main view sometimes jumps back to Chief's chat on its own.
Looked at, not reproduced and not fixed (no live browser session available to the investigation):
- No plugin code opens Chief on its own: every
actions.openSessioncall in the social client is a user action or the Face-to-face join/start flow. - Candidates in core: the Bot-mode
home()fallback (index.js, opens the Main Bot when the main view holds a Session that is in neitherroster.byIdnorroster.roomsById), which would fire if the friend chat's Bot record is briefly hidden/gonewhileremote.chats.syncrewrites it; andlandOnwhen a chat part is archived for a fresh one.
To do: reproduce with a roster refresh on a friend chat (sync marking the remote Bot gone/hidden for a poll) and log which path calls openSession. If it is home(), a friend chat must count as known while it is only hidden.
Activity
Birfy commentedon Oct 18, 2026
Re-checked live on A (:3080) and B (:3081) with A's tab left open while B was used (~4 min each, plus a test message from B): no jump reproduced. PR #280 (merge 2ee01fe) makes an emptied main view return to the same chat instead of the Main Bot, and logs every openSession/landOn without user activation with its caller to diagnostics/console. Leaving this open until it is confirmed on upgraded instances; if it recurs, the diagnostics will name the caller.
Birfy commentedon Oct 18, 2026
Still not reproduced; leaving open. No code change this maintenance run.
Birfy commentedon Oct 18, 2026
Possible lead from the self-test on
a003044(2026-10-18 16:25, fresh A/B): right after B accepted A's invite, A's home created a friend-chat record for B's unshared Chief.remoteBots()publishes the unfiltered roster first, beforesyncOutgoingGrants()letskeepGrantedRemote()drop reverse-friends. 34 s later the re-filter marked itgone+hidden, and on the next load A opened that dead chat. This is the same "briefly listed, then gone/hidden" flip suspected here, so thehome()/ open-on-load paths should treat a hidden/gone chat consistently. Details: #303.Birfy commentedon Oct 19, 2026
Triage on main
7b9e90b, 2026-10-19 ~12:10 Asia/Shanghai: still open, needs-info. Not reproduced; #280 added diagnostics that log anyopenSession/landOnwithout user action and its caller. Blocking: a live repro (or a diagnostics line naming the caller) on current main. Possibly related to the hidden/gone flip in #303.Birfy commentedon Oct 19, 2026
Triage on main
0852b3f, 2026-10-19 16:59 Asia/Shanghai: still needs-info. Nothing in the code answers this. #280 logs everyopenSession/landOnthat runs without a user action, with its caller, and #303 (the hidden/gone flip, the likely trigger) was fixed on 2026-10-18. This may be fixed already, but it has not been confirmed live.Repro for the next friend-DM self-test: on A, open a friend's Bot chat right after accepting a fresh invite, which is when the old #303 flip happened. Leave it open for about 10 min while B sends 2-3 lines and A's roster polls. Then reload once. Watch whether the main view leaves the friend chat. Afterwards, search A's diagnostics/console for the #280 "openSession/landOn without user activation" lines.
Birfy commentedon Oct 19, 2026
Maintenance triage (2026-10-19 20:01 Asia/Shanghai, main
753b7e9): still needs-info. No new live self-test since the 16:59 check. Leaving open; next face/friend self-test should run the repro notes on the previous comment. Not pushing design questions while this waits on live confirmation.Birfy commentedon Oct 20, 2026
Triage (2026-10-20 12:00 Asia/Shanghai, main a7adfe0): still needs-info. None of today's face-room/friend routing merges (#465, #467, #468, #487, #488) touch the client paths suspected here: the Bot-mode
home()fallback incore/src/client/index.js(still present, it runs on switching back to Bot mode) andlandOn. So this is not clearly fixed by code. #280 diagnostics and the #303 fix are in. Still needed: one live run of the repro in the 2026-10-19 16:59 comment on current main, plus any "openSession/landOn without user activation" diagnostics line. If there is no jump and no such line, close.Birfy commentedon Oct 20, 2026
Triage (2026-10-20 16:05 Asia/Shanghai, main
787a502which includes #516/#491/#478/#484): still needs-info. No new live repro since the 2026-10-19 notes. #280 diagnostics and the #303 fix remain the best leads; recent social merges do not touch the Bot-modehome()/landOnpaths suspected here.Still needed (one concrete outcome): run the repro in the 2026-10-19 16:59 comment on current main — open a friend Bot chat right after a fresh invite, leave it ~10 min with a couple of friend lines and roster polls, then reload once.
#280"openSession/landOn without user activation" diagnostics line → please say so here and we will close as obsolete.Leaving open; not inventing a code fix without that signal.