You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting a debug session and then restarting the console, this extension used to reset the debug status in vscode. It no longer does and users may erroneously think that debug is "running" even though all breakpoints have been cleared by the session restart.
Often a "timeout after 1000ms" will come up as well, I assume something in omnisharp isn't being notified when a session restart takes place?
Extension version: 2020.6.1
VS Code version: Code - Insiders 1.47.0-insider (7e4cc2c435927e5a2845897961a2af10ee7f784d, 2020-06-12T06:03:53.183Z)
OS version: Windows_NT x64 10.0.19041
System Info
Item
Value
CPUs
Intel(R) Core(TM) i5-1035G7 CPU @ 1.20GHz (8 x 1498)
Issue Type: Bug
When starting a debug session and then restarting the console, this extension used to reset the debug status in vscode. It no longer does and users may erroneously think that debug is "running" even though all breakpoints have been cleared by the session restart.
Often a "timeout after 1000ms" will come up as well, I assume something in omnisharp isn't being notified when a session restart takes place?
Extension version: 2020.6.1
VS Code version: Code - Insiders 1.47.0-insider (7e4cc2c435927e5a2845897961a2af10ee7f784d, 2020-06-12T06:03:53.183Z)
OS version: Windows_NT x64 10.0.19041
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: