Repository navigation
Run in terminal request stuck due to bad quoting stuck in line continuation #254426
Copy link
Copy link
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugchat-terminalThe run in terminal tool in chatThe run in terminal tool in chat
Milestone
Description
Activity
- assigned and unassigned
on Jul 7, 2025 - addedbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugchat-terminalThe run in terminal tool in chatThe run in terminal tool in chat
on Jul 23, 2025 - changed the title
[-]Github Copilot Chat stuck in terminal[/-][+]Run in terminal request stuck due to bad quoting stuck in line continuation[/+]on Jul 23, 2025 Daniel Imms (@Tyriar) - for me getting stuck on
dquoteis the most common case for GHCA to get stuck in the past months.Any chance to get that fixed?
Here's the latest case where it happened today.
Hope it helps to pinpoint the issue.
cdeil@Mac android % patrol test && echo "Tests passed!" || if [[ -f "build/app/reports/androidTests/connected/index.html" ]]; then echo "Tests executed, check results"; else echo "Test execution failed "; fi cmdand dquote>### Solution 3: Check Test Results Programmatically You can parse the test results file to determine the actual test status: 🛠️ run_in_terminal (toolu_vrtx_015ATa2LD2wh3aPX7vAXgZAL) { "command": "patrol test && echo \"Tests passed!\" || if [[ -f \"build/app/reports/androidTests/connected/index.html\" ]]; then echo \"Tests executed, check results\"; else echo \"Test execution failed\"; fi", "explanation": "Testing a command to distinguish between test failures and execution failures", "isBackground": false }
ghirardinicola commented
on Jan 15, 2026 More actionsSame for me. Using long parms Is impossible. Did not found a workaround year
Daniel Imms (@Tyriar) - for me getting stuck on
dquoteis the most common case for GHCA to get stuck in the past months.Any chance to get that fixed?
Here's the latest case where it happened today.
Hope it helps to pinpoint the issue.
cdeil@Mac android % patrol test && echo "Tests passed!" || if [[ -f "build/app/reports/androidTests/connected/index.html" ]]; then echo "Tests executed, check results"; else echo "Test execution failed "; fi cmdand dquote>### Solution 3: Check Test Results Programmatically You can parse the test results file to determine the actual test status: 🛠️ run_in_terminal (toolu_vrtx_015ATa2LD2wh3aPX7vAXgZAL) { "command": "patrol test && echo \"Tests passed!\" || if [[ -f \"build/app/reports/androidTests/connected/index.html\" ]]; then echo \"Tests executed, check results\"; else echo \"Test execution failed\"; fi", "explanation": "Testing a command to distinguish between test failures and execution failures", "isBackground": false }
- assigned and unassigned
on Mar 24, 2026 meganrogge commented
on Mar 25, 2026 CollaboratorMore actionsI believe this is already fixed, can you see if you can reproduce in the Insiders build?
- locked and limited conversation to collaborators
on May 9, 2026
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugchat-terminalThe run in terminal tool in chatThe run in terminal tool in chat
Does this issue occur when all extensions are disabled?: N/A
Steps to Reproduce:
dqoute>Example command:
Slight workaround:
Send a message of
dqoute>, GHCP Chat will recognise the terminal is hanging, and will continue.Or attempt to manually
EOLthe terminal to enter command.Unsure if this is the model itself, or GHCP Chat, as it can adapt if aware.