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
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseverifiedVerification succeeded
sandy081
added
bug
Issue identified by VS Code Team member as probable bug
candidate
Issue identified as probable candidate for fixing in the next release
labels
Nov 12, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseverifiedVerification succeeded
Issue Type: Bug
Was this an intentional change?
For instance, in the Cosmos DB extension (ms-azuretools.vscode-cosmosdb):
Version: 1.28.2 (user setup):
VS Code version: Code - Insiders 1.29.0-insider (5438af1, 2018-11-07T01:01:54.305Z):
The corresponding view/item/context items look like:
{
"command": "cosmosDB.copyConnectionString",
"when": "view == cosmosDBExplorer && viewItem == cosmosDBGraphAccount"
},
{
"command": "cosmosDB.createGraphDatabase",
"when": "view == cosmosDBExplorer && viewItem == cosmosDBGraphAccount"
},
System Info
checker_imaging: disabled_off
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: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Extensions (10)
The text was updated successfully, but these errors were encountered: