fix: drain queued branch sessions from backend lifecycle#579
Conversation
Drain the next queued branch session after orphaned running sessions are recovered at startup. Reuse the app session registry during recovery and clarify the queue-drain and branch-resolution assumptions in docs.
Re-add the commands API import in sessionStatusListener so PR and push completion handlers typecheck again after the queue-drain cleanup removed the import.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2205fe491c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| import { listen, type UnlistenFn } from '@tauri-apps/api/event'; | ||
| import * as commands from '../api/commands'; | ||
| import { |
There was a problem hiding this comment.
The listener still uses commands.getSessionMessages, commands.updateBranchPr, commands.refreshPrStatus, and commands.clearBranchPrStatus, but this commit removed the commands import. That makes PR/push completion handling fail (TypeScript compile error or runtime ReferenceError when those handlers run), so users will lose PR URL parsing/status updates after sessions complete.
Useful? React with 👍 / 👎.
1 participant
Summary