CTRL+SPACE triggers constant debugging loop when editing during debug phase

[PrzemyslawKlys]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

I have started to notice this in last 1 or 2 versions. Basically I press F9 to stop on something in code. I then press F5, the code goes and stops on specific value. I then edit that value and then cancel with SHIFT+F5. Debugging stops, now I go to that value and type CTRL+SPACE (I am not sure if something else triggers it, probably yes, and debugging resumes out of nowhere.

This gif shows this

PowerShell Version

PSVersion                      7.4.0-preview.1
PSEdition                      Core
GitCommitId                    7.4.0-preview.1
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.74.3
97dec172d3256f8ca4bfb2143f3f76b503ca0534
x64

Extension Version

ms-vscode.powershell@2022.12.1                                                                                                                                                                                                                                                                          
ms-vscode.powershell-preview@2023.1.0                                                                                                                                                                                                                                                                   
tobysmith568.run-in-powershell@1.1.1                                                                                                                                                                                                                                                                    
TylerLeonhardt.vscode-inline-values-powershell@0.0.7

Steps to Reproduce

As described above

Visuals

No response

Logs

EditorServices.zip

[ninmonkey]

I couldn't reproduce it, although in the past sometimes I had an issue when there's no launcher defined.

• If you place this in your global settings.json, is there any difference?

{
    "launch": {
        "version": "0.2.0",
        "configurations": [
            { "name": "Cur.ps1 🏃‍♂️", "type": "PowerShell", "request": "launch", "script": "${file}",
              "presentation": { "hidden": false, "group": "Invoke-Run", "order": 1 }, "cwd": "${file}" 
            },
        ],
        "compounds": []
    },
}

The log looked mostly normal, until this section.

2023-01-14 20:19:43.891 +01:00 [DBG] Queueing "Serial":exit request for processing
2023-01-14 20:19:43.891 +01:00 [DBG] Starting: Processing notification exit
2023-01-14 20:19:43.892 +01:00 [DBG] Starting: Routing Notification exit
2023-01-14 20:19:43.892 +01:00 [VRB] Converting params for Notification exit to OmniSharp.Extensions.LanguageServer.Protocol.Models.ExitParams
2023-01-14 20:19:43.895 +01:00 [DBG] Shutting down host...
2023-01-14 20:19:43.895 +01:00 [VRB] Could not write to output handler, perhaps serialization failed?
System.Threading.Channels.ChannelClosedException: The channel has been closed.
   at System.Threading.Channels.AsyncOperation`1.GetResult(Int16 token)
   at OmniSharp.Extensions.JsonRpc.OutputHandler.ProcessOutputStream(CancellationToken cancellationToken)
2023-01-14 20:19:43.896 +01:00 [DBG] Finished: Routing Notification exit in 4ms
2023-01-14 20:19:43.896 +01:00 [DBG] Finished: Processing notification exit in 4ms
2023-01-14 20:19:43.896 +01:00 [FTL] unhandled exception
OmniSharp.Extensions.JsonRpc.InputProcessingException: There was an error processing input the contents of the buffer were ''
 ---> System.InvalidOperationException: Reading is not allowed after reader was completed.
   at System.IO.Pipelines.ThrowHelper.ThrowInvalidOperationException_NoReadingAllowed()
   at System.IO.Pipelines.Pipe.AdvanceReader(SequencePosition& consumed, SequencePosition& examined)
   at OmniSharp.Extensions.JsonRpc.InputHandler.ProcessInputStream(CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at OmniSharp.Extensions.JsonRpc.InputHandler.ProcessInputStream(CancellationToken cancellationToken)
   at OmniSharp.Extensions.JsonRpc.InputHandler.ProcessInputStream(CancellationToken cancellationToken)
   at OmniSharp.Extensions.JsonRpc.InputHandler.<Start>b__26_0()

Ideas

• Try moving the default hotkey. shift+f5 has two bindings, disconnect and stop Maybe the when condition is running disconnect instead of stop ?

• Sometimes exceptions are being thrown but they never render. Set your prompt to this, before you run the test.

function prompt {@(
   "`n`n"
   Get-Location
   # note: global scope is required to access the correct scope
   # without it, if you set a breakpoint in a module
   # otherwise breakpoints inside a module will return the wrong error count
   $global:error.Count
   'Pwsh> '
)-join "`n"}

[ninmonkey]

Oh I have an idea. If that fixes it for you, then I think the cause is here

• this locks up for a few seconds when I hit ctrl+space
• it's a fairly recent behavior

To fix

I disable shellIntegration

"terminal.integrated.shellIntegration.enabled": false,

then: Powershell: Restart Session
Now ctrl+space does not lag or lock up.

to reproduce

When this is enabled

"terminal.integrated.shellIntegration.enabled": true,

• I'm paused in a breakpoint
• I type a wildcard command, in the debug term, then hit ctrl+space

• It locks up for a few seconds

• then it opens help page in a pager

• hit quit then I'm back to my breakpoint

Locate Shell Integration Script

code --locate-shell-integration-path pwsh

[ninmonkey]

I'm not sure if it's shellintegration itself, or, if it's indirectly conflicting with the default f12 key (which is a recent addition)

---

Outside of vs code

• my f12 key calls the new ShowCommandHelp function.
• ctrl+space calls menu complete like normal

Keybinds

Ps G:\temp\random> get-psreadlinekeyhandler | ? function -match '(command.*help)|complete'

Completion functions
====================

Key           Function            Description
---           --------            -----------
Ctrl+@        MenuComplete        Complete the input if there is a single completion, otherwise complete
Ctrl+Spacebar MenuComplete        Complete the input if there is a single completion, otherwise complete
Tab           TabCompleteNext     Complete the input using the next completion
Shift+Tab     TabCompletePrevious Complete the input using the previous completion

Miscellaneous functions
=======================

Key Function        Description
--- --------        -----------
F1  ShowCommandHelp Shows help for the command at the cursor in an alternate screen buffer.
F12 ShowCommandHelp Shows help for the command at the cursor in an alternate screen buffer.

[andyleejordan]

@ninmonkey I think you're onto something, there's this in the shell integration script:

# Set always on key handlers which map to default VS Code keybindings
function Set-MappedKeyHandler {
	param ([string[]] $Chord, [string[]]$Sequence)
	$Handler = $(Get-PSReadLineKeyHandler -Chord $Chord | Select-Object -First 1)
	if ($Handler) {
		Set-PSReadLineKeyHandler -Chord $Sequence -Function $Handler.Function
	}
}

function Set-MappedKeyHandlers {
	Set-MappedKeyHandler -Chord Ctrl+Spacebar -Sequence 'F12,a'
	Set-MappedKeyHandler -Chord Alt+Spacebar -Sequence 'F12,b'
	Set-MappedKeyHandler -Chord Shift+Enter -Sequence 'F12,c'
	Set-MappedKeyHandler -Chord Shift+End -Sequence 'F12,d'
}

Set-MappedKeyHandlers

For shell integration, we're importing Code's script upstream as close to the original as possible, hence these are included. @SeeminglyScience is wondering if there's something client-side we're missing.

[andyleejordan]

Wait, @PrzemyslawKlys, you're in the file buffer when you press Ctrl+Space right, as in, triggering VS Code completions? So we're not in PSReadLine, if so, ignore the above comment.

[andyleejordan]

Ok @ninmonkey I think you're experiencing a totally different issue, and that's just that we think you have your own binding for F12 to Get-Help, and VS Code's shell integration stomps on that.

@PrzemyslawKlys I think you're seeing that asking for completions is triggering the state-sync logic to think that the debugger is supposed to resume/stop.

This issue was closed automatically as author feedback was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information!

[PrzemyslawKlys]

I am not sure if I should respond or not. My issue is different than what ninmonkey has. It's related to strictly editing within code pane while in debug, which triggers continue and then is stuck in a loop.