Skip to content

[2020.1.0 Preview] F8 not working while using "Interactive Session" debuging #2424

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

Closed
ili101 opened this issue Jan 16, 2020 · 3 comments · Fixed by PowerShell/PowerShellEditorServices#1209
Labels
Milestone

Comments

@ili101
Copy link

ili101 commented Jan 16, 2020

Issue Type: Bug

Start.ps1

. .\File2.ps1

File2.ps1

1
2
3

.vscode\launch.json

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "PowerShell Launch Current File",
            "type": "PowerShell",
            "request": "launch",
            "script": "${file}",
            "cwd": "${file}"
        },
        {
            "name": "PowerShell: Interactive Session",
            "type": "PowerShell",
            "request": "launch",
            "cwd": ""
        }
    ]
}
  1. Start "PowerShell: Interactive Session" debug.
  2. Set breakpoint anywhere on File2.ps1.
  3. Go to Start.ps1 and F8 on the line (debug will start and take you to the breakpoint on File2.ps1).
  4. F8 on any line (it will not work).
  5. F5 to finish debugging (All previous F8s will execute at once after the script finished).

F8

Logs:
EditorServices.log
F8 presses are the 2020-01-17 00:39:29.212 +02:00 [DBG] Finding descriptor for evaluate log lines. The lines after that are the F5

Extension version: 2020.1.0
VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:58:56.166Z)
OS version: Windows_NT x64 10.0.18363

System Info
Item Value
CPUs AMD Ryzen 7 1800X Eight-Core Processor (4 x 3593)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: unavailable_off
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 4.00GB (1.36GB free)
Process Argv
Screen Reader no
VM 100%
@ghost ghost added the Needs: Triage Maintainer attention needed! label Jan 16, 2020
@rjmholt rjmholt added Area-Debugging Issue-Bug A bug to squash. and removed Needs: Triage Maintainer attention needed! labels Jan 17, 2020
@rjmholt
Copy link
Contributor

rjmholt commented Jan 17, 2020

I'm able to reproduce this. Looking into it

@ili101
Copy link
Author

ili101 commented Feb 23, 2020

Still a problem on 2020.2.0 Preview

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Feb 23, 2020
@rjmholt rjmholt added this to the 2.0.0 milestone Feb 24, 2020
@SydneyhSmith SydneyhSmith removed the Needs: Maintainer Attention Maintainer attention needed! label Feb 25, 2020
@TylerLeonhardt
Copy link
Member

PR out for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants