Repository navigation
fix(discord-bot): persist T3 bearer and keep local bootstrap past 24h - #414
Merged
Merged
Conversation
The colocated Discord bot re-exchanges local-bootstrap-credential on every restart. PairingGrantStore seeded that file with the desktop 24h TTL, so a bot-only restart more than a day after t3code-server start failed forever with invalid_credential. Keep the desktop IPC seed at 24h. Give the file-backed local grant a long-lived TTL, and persist the 30-day bearer so restarts do not depend on re-bootstrap.
@electron/asar 3.4's unpack matcher does not treat **/*.node as matching nested files on this host, so packWindowsServerAsar failed its unpacked-dir check in the local ship gate. Include basename globs too so both dialects unpack.
patroza
marked this pull request as ready for review
August 20, 2026 07:05
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
Omegent on t3vm failed with
T3 did not become ready after a server restartbecause the Discord bot re-exchangeslocal-bootstrap-credentialon every process start, and that grant was seeded with the desktop 24h TTL. Aftert3code-serverhad been up more than a day, a bot-only restart (or a deploy that restarted only the bot) loopedinvalid_credentialforever.*.nodeas well as**/*.node) sopackWindowsServerAsarstill createsserver.asar.unpackedon hosts where@electron/asar3.4 does not treat**as nested.Test plan
PairingGrantStorelocal-file grant still consumes after 25h and 400dbuild-desktop-artifactWindows asar unpack tests/is 200 again