fix(tui): open connect dialog when no agencies are discovered - #329
Merged
Conversation
- Route the existing no-agencies discovery error through the fork-owned connect recovery dialog. - Cover the exact session error while leaving discovery, resolver, and copy unchanged.
Contributor
|
The following comment was made by an LLM, it may be inaccurate: |
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.
Issue for this PR
Fixes #328
Type of change
What does this PR do?
The fork-owned TUI classifier did not recognize the existing provider-scoped no-agencies discovery error. This change classifies that exact error so the existing
/connectdialog opens, without changing discovery, resolution, error copy, dialog UI, or multiple-agency behavior.How did you verify your code works?
1.4.40and SHA-25682bb0cd61aa416abd7b1962f343bb075ffa5bbc80b340d352376f73a006af022.59475, made three discovery requests to that port, and exited cleanly without process or repository drift.Screenshots / recordings
Not applicable; the existing dialog UI and copy are unchanged.
Checklist