Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Insiders is not showing full object values in Debug Console or value tooltip #49927

Closed
StephenWeatherford opened this issue May 15, 2018 · 2 comments
Closed

Insiders is not showing full object values in Debug Console or value tooltip #49927

StephenWeatherford opened this issue May 15, 2018 · 2 comments
Assignees
@isidorn
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone
May 2018

Comments

@StephenWeatherford
Copy link

Issue Type: Bug

I'm debugging an extension (therefore Node.js)

1.23.1:
image

Insiders:
image

Easiest to repro:

  1. While debugging Node.js:
  2. Type this into debug console:
    {a:{b:"hi"}}
  3. Try expanding it
    !) No additional data shows up

1.23.1:
image

Insiders:
image

VS Code version: Code - Insiders 1.24.0-insider (5d12f53, 2018-05-14T05:16:26.538Z)
OS version: Windows_NT x64 10.0.16299

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E31230 @ 3.20GHz (4 x 3193)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
video_decode: enabled
video_encode: enabled
vpx_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 15.96GB (5.86GB free)
Process Argv C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe C:\Repos\vscode-azurearmtools
Screen Reader no
VM 0%
Extensions (9)
Extension Author (truncated) Version
json-tree-view Cha 1.1.0
vscode-markdownlint Dav 0.16.0
tslint eg2 1.0.28
vscode-azurestorage ms- 0.3.1
vscode-cosmosdb ms- 0.7.1
vscode-language-pack-de MS- 1.23.2
azure-account ms- 0.4.0
azurerm-vscode-tools msa 0.4.1
antlr4 nct 0.0.1
@isidorn
Copy link
Contributor

isidorn commented May 16, 2018

@StephenWeatherford thanks for this great catch and for using insiders.
This was caused by my refactoring of how the debug session connects to the extension host for extension debugging.
A fix is to actually just remove the inactive state for the debug session since it is actually not used anywhere in a useful way.

Verifier

  1. Start debugging an extesnion
  2. Type this into debug console:
    {a:{b:"hi"}}
  3. Verify it expands properly

@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels May 16, 2018
@isidorn isidorn added this to the May 2018 milestone May 16, 2018
@StephenWeatherford
Copy link
Author

Thanks!

@RMacfarlane RMacfarlane added the verified Verification succeeded label May 31, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@isidorn isidorn

Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Milestone
May 2018
Development

No branches or pull requests
3 participants
@isidorn @RMacfarlane @StephenWeatherford