-
-
Notifications
You must be signed in to change notification settings - Fork 430
fix: remap text/both input_mode from config file in TUI to avoid stdin conflict #193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
octo-patch
wants to merge
1
commit into
dnhkng:main
Choose a base branch
from
octo-patch:fix/issue-188-text-input-mode-tui-stdin-conflict
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: dnhkng/GLaDOS
Length of output: 4007
Don't inject an undeclared
input_modevalue.Lines 1410 and 1422 write
"none"toinput_mode, butGladosConfig.input_modeis declared asLiteral["audio", "text", "both"]and the engine only branches on those three values. When this config is passed toGlados.from_config(), the"none"value will violate the type contract and cause bothspeech_listenerandtext_listenerto be silently skipped without explicit intent.Either extend the
input_modeLiteral type to include"none"across config and engine layers, or suppressTextListenerusing a separate TUI-only flag while keepinginput_modewithin its declared contract.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the options to fix this? Pros and cons for both please
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 11804
@dnhkng, here's a breakdown of both options with the engine code as context.The engine's
__init__decides what to start based oninput_modevia two independent guards:When
"none"is passed today, neither branch matches, so both listeners are silently skipped — it works, but only by accident.Option A — Extend
input_modeto formally include"none"Make
"none"a first-class value inGladosConfig,Glados.__init__, and the YAML schema.Changes required:
GladosConfig.input_mode: Literal["audio", "text", "both", "none"] = "audio"(engine.py line 110)Glados.__init__()parameter (line 201)elif self.input_mode == "none": logger.info("Input disabled.")branch for clarityPros:
Cons:
input_mode: nonewill now be valid (could be surprising)Option B — Add a TUI-only
suppress_text_listenerflagKeep
input_modeasLiteral["audio", "text", "both"]and introduce a separate boolean inGladosConfig(e.g.tui_mode: bool = False) that the engine checks when startingTextListener.Changes required:
tui_mode: bool = FalsetoGladosConfigandGlados.__init__()TextListenerguard in engine toif self.input_mode in {"text", "both"} and not self.tui_modetui.py, setupdates["tui_mode"] = Trueinstead of remappinginput_modeto"none"or"audio"; keepinput_modeunchangedPros:
input_modecontract stays strictly intacttui.pybecomes simpler (no need to translate values)/status,/config) still report the user's original intentCons:
tui_mode) leaks into the engine and config schema — breaks separation of concerns__init__signature, and TUITextListenerRecommendation
Option A is the cleaner path. The engine's existing
if ... in {"audio", "both"}/if ... in {"text", "both"}pattern already excludes"none"correctly — the only gap is the missing type declaration. A two-line type annotation change formally closes that gap without introducing cross-layer coupling.