jinglouMSFT
jinglouMSFT
The VS Code bug was closed due to lack of a generic repro step. The issue is similar to VS Code command: Git: Clone, where the content of the wizard...
@MicroFish91 @12-shweta VS Code has closed the bug as merged. Although the solution doesn't seem to be 100% reliable. Can you try this in the Functions extension? Make sure you...
@12-shweta you need to download the "Quickinput sample" extension, then you need to open the folder where you have the sample source code in VS Code and open the "Terminal"...
@12-shweta Since this is a VS Code bug, can you make this a tracking bug on our side? There is no action on our side but it's showing up in...
@sohelmulani1998 The upstream bug has been closed as by design https://github.com/microsoft/vscode/issues/52016. How would you like to resolve our bug (this bug)?
Per discussion, let's add a status update to the activity log: - when/after pinning a node to Quick Access - when/after unpinning a node from Quick Access Also, add a...
Let's discuss if this can be done in v1.26.0
Sounds like a good plan
Are you using Storage Explorer behind a proxy server? If yes, please take a look at this section in the Storage Explorer troubleshooting guide: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-troubleshooting?tabs=Windows%2C2004#proxy-issues to see if any suggested...
There is a section in the Troubleshooting guide that discusses in details about the proxy settings. Here is the link https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-network. The error on tunneling socket usually indicates that Storage...