fix(discord-bot): survive guest T3 restarts without stuck project lookups - #137
Merged
Merged
Conversation
…kups Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure.
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza
added a commit
that referenced
this pull request
Jul 28, 2026
…kups (#137) Boot used a single connect attempt and could mark the session ready before the shell snapshot arrived, so mentions after a restart looked like missing projects and stayed broken until a manual bot restart. Retry connect until shell-ready, tear down partial sessions, force reconnect on transport errors, and surface a transient "still connecting" message instead of a false alias/path failure. Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
After a guest/server restart, Discord can come READY before T3 is listening. The bot either exited on first connect failure or connected without a shell snapshot, so later mentions looked like “no T3 project registered at path” and stayed stuck until a manual bot restart.
connectUntilReadyretries forever with the same backoff as mid-life reconnect (process stays up).RpcSession.closedis slow/missed (no auto-retry of the command — avoids double-start).Test plan
vp test run src/t3/T3Session.test.ts(transport error helpers + existing model tests)vp checkon changed files