Exception showing on Scope variables

[wsmelton]

Issue Type: Bug

Begin debugging session for Pester tests.
Added misspelled expression to Watch panel
Hit F10 a few times and F11
Renamed expression
Tried to add a second one, the plus sign grayed out and not able to add anymore.

Extension version: 2020.9.0
VS Code version: Code - Insiders 1.51.0-insider (6c8c6008ef9d86e46b086a00f273b1fee5bd8c51, 2020-10-21T05:39:35.557Z)
OS version: Windows_NT x64 10.0.19041

PSEditorService_Output.txt

View of the Watch panel when this happened, after a few seconds the original expression I added and renamed goes away. Then when I click on the plus sign to try and add another one it seems to show an empty item:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: enabled rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.88GB (14.19GB free)
Process Argv	--crash-reporter-id c13a5331-9871-4944-a4d0-0f26ca06b445
Screen Reader	no
VM	33%

[wsmelton]

For the most part a lot of these are being written:

Parameter name: scopeID
Actual value was 7. ---> System.Management.Automation.PSArgumentOutOfRangeException: The scope number '7' exceeds the number of active scopes.
Parameter name: scopeID
Actual value was 7.
   at System.Management.Automation.SessionStateInternal.GetScopeByID(Int32 scopeID)
   at System.Management.Automation.SessionStateInternal.GetScopeByID(String scopeID)
   at System.Management.Automation.SessionStateInternal.GetVariableTableAtScope(String scopeID)
   at Microsoft.PowerShell.Commands.VariableCommandBase.GetMatchingVariables(String name, String lookupScope, Boolean& wasFiltered, Boolean quiet)
   at Microsoft.PowerShell.Commands.GetVariableCommand.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
   at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.InvokeWithDebugger(IEnumerable`1 input, IList`1 output, PSInvocationSettings settings, Boolean invokeMustRun)
   at System.Management.Automation.ScriptDebugger.ProcessCommand(PSCommand command, PSDataCollection`1 output)
   at Microsoft.PowerShell.EditorServices.Services.PowerShellContext.PowerShell5Operations.ExecuteCommandInDebugger[TResult](PowerShellContextService powerShellContext, Runspace currentRunspace, PSCommand psCommand, Boolean sendOutputToHost, Nullable`1& debuggerResumeAction)
   at Microsoft.PowerShell.EditorServices.Services.PowerShellContextService.ExecuteCommandInDebugger[TResult](PSCommand psCommand, Boolean sendOutputToHost)
   at Microsoft.PowerShell.EditorServices.Services.PowerShellContextService.<ExecuteCommandAsync>d__89`1.MoveNext() | 
[Error - 7:28:53 AM] Microsoft.PowerShell.EditorServices.Services.PowerShellContextService: Execution of the following command(s) completed with errors:

    Get-Variable -Scope 7

[SydneyhSmith]

Thanks @wsmelton looks like this area of the code could be more robust with better errors.
It would be helpful to know more context around what you were doing when you hit this issue-- for example what modules you were debugging, or anything particular about your set up

[wsmelton]

I don't know if anything that was specific. I'm using Pester 5.1 (beta release) with the PS preview extension, confirmed issue does not exist in the stable release.

I have a module workspace in VS Code opened:

Then I'm debugging the File Integrity script which I've shared in this Gist on Twitter as well: https://gist.github.com/wsmelton/24bad5e8fbe4ca8f47b9bdb7f25e556d

You can simply:

1. add one or two breakpoints
2. hit F5 (I'm using interactive config)
3. Call Invoke-Pester .\tests\Module.FileIntegrity.Tests.ps1
4. Go through hitting F10 and F11 a few times (debugger will jump into the Pester.psm1 file)
5. Add an expression and it greyes out that plus sign and the UI won't let you add the expression

I am on VS Code Insiders and received the past few updates that have been pushed and this still happens.

[SydneyhSmith]

Thanks @wsmelton when you go to add the expression is the breakpoint stopped inside your test file or inside Pester.psm1?

[wsmelton]

Yep, just checked again and it won't happen until the debugger steps into the Pester.psm1 file.

[SydneyhSmith]

Thanks @wsmelton for all the information--this looks similar to a bug our intern experienced with debugging scripts running in GitHub actions...this will be a good example for us to work off of to investigate this.