Not able to report issues while container is starting

[JacksonKearl]

Issue Type: Bug

When connecting to a new remote container, the extensions view does not load, and I am unable to report an issue.

Extension version: 0.102.0
VS Code version: Code - Insiders 1.43.0-insider (e6a45f4, 2020-02-21T05:39:20.465Z)
OS version: Darwin x64 18.7.0
Fetching remote diagnostics for 'dev-container+2f55736572732f6a6b6561726c2f446576656c6f7065722f7673636f64652d72656765782d72757374' timed out.

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)
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: 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
Load (avg)	2, 2, 2
Memory (System)	32.00GB (7.28GB free)
Process Argv
Screen Reader	no
VM	0%

Fetching remote diagnostics for 'dev-container+2f55736572732f6a6b6561726c2f446576656c6f7065722f7673636f64652d72656765782d72757374' timed out.

[RMacfarlane]

@JacksonKearl Is this from using the "Report Issue" item under "Help and Feedback"? Or just opening the issue reporter normally?

[JacksonKearl]

@RMacfarlane I found "Help: Report Issue" in command pallette is a no-op while the container is initializing.

[sandy081]

Not sure how it is related to extensions view?

[JacksonKearl]

@sandy081 made a separate issue for extensions view.