Does this occur consistently?
Repro steps:

Action: azureCognitiveSearch.searchDocument.onDidSaveTextDocument
Error type: Error
Error Message: The request is invalid.

Version: 0.2.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.56.2
Language: en

SimpleSearchClient.<anonymous> extension.bundle.js:5:209545
rejected extension.bundle.js:5:206203
processTicksAndRejections task_queues.js:93:5

Hello 👋 I'm from the VS Code team.

Recently, we have been exploring a security feature we refer to as Workspace Trust. This feature is intended to centralize and unify a security conscious decision required by a variety of VS Code features. With workspace trust, the user will be able to declare whether or not they trust the folder that is opened in VS Code before these features are executed.

Why you should care

Your extension is incredibly popular with VS Code users! We want to make sure that those users have a delightful experience with workspace trust and that includes extension authors deciding how much of their extension is supported in an untrusted workspace.

Workspace Trust experience

You can enable the feature with the following setting security.workspace.trust.enabled. Once enabled, you will see the following dialog when opening folders in VS Code.

This dialog is important for allowing the user to make a decision early and understand the impact of their decision. Once you understand the feature, you may want to customize when to display the dialog using the setting security.workspace.trust.startupPrompt.

You can follow the development of Workspace Trust and provide feedback in issue #106488.

Workspace trust API

First off, all of what I am about to say can be found in issue #120251. That issue will include discussion of the feature and any updates to the feature.

The Workspace Trust extension API is now in stable. This allowed us to release the first cut of our guide for onboarding your extension to Workspace Trust. The API is small, so here is a quick look.

You can declare your extension to provide complete, partial or no support in untrusted workspaces using the untrustedWorkspaces capability in package.json.

The following example declares that the extension is supported completely in untrusted workspaces. In this case, the extension is enabled in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": true
  }
}

The next example declares that the extension is not supported in untrusted workspaces. In this case, the extension is disabled in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": false
  }
}

The third option is to declared limited support. There are three tools provided to you when you select the limited option.

First, if you have a setting that can be configured in the workspace but requires the workspace to be trusted in order to apply the workspace value, then you can include the setting using restrictedConfigurations array property in untrustedWorkspaces object. Doing so, VS Code will ignore the workspace value of these restricted settings when your extension reads these settings values using the VS Code Workspace Configuration API.

The following example declares the settings that are restricted in untrusted workspaces.

"capabilities": {
  "untrustedWorkspaces": {
    "supported": "limited",
    "restrictedConfigurations": [
      "markdown.styles"
    ]
  }
}

Next, you can also check and listen if the current workspace is trusted or not programmatically using the following API:

export namespace workspace {
  /**
   * When true, the user has explicitly trusted the contents of the workspace.
   */
  export const isTrusted: boolean;
  /**
   * Event that fires when the current workspace has been trusted.
   */
  export const onDidGrantWorkspaceTrust: Event<void>;
}

Lastly, you can hide commands or views declaratively with the isWorkspaceTrusted context key in your when clauses.

A far more detailed guide on how to onboard which will be updated as we receive feedback can be found in issue #120251.

Rollout plan

Workspace Trust will remain disabled for the month of May, but we are planning on enabling this by default in the future. To prepare for that day, we would love for you to try it out and provide feedback.

We'd love your feedback

Since this issue was created in an automated fashion, we won't be monitoring the responses in this issue (our notifications would explode!). Instead we ask you to drop questions, and feedback in issue #120251 as we've mentioned above.

We're excited to see what you do with workspace trust!

Does this occur consistently?
Repro steps:

Action: azureCognitiveSearch.search
Error type: Error
Error Message: Entry not found in cache.

Version: 0.3.1
OS: win32
OS Release: 10.0.22000
Product: Visual Studio Code
Product Version: 1.70.1
Language: en

Logger.createError extension.bundle.js:2:820371
TokenRequest.<anonymous> extension.bundle.js:2:845807
extension.bundle.js:2:840157extension.bundle.js:2:840157
extension.bundle.js:2:812478extension.bundle.js:2:812478
extension.bundle.js:2:811641extension.bundle.js:2:811641
extension.bundle.js:2:833247extension.bundle.js:2:833247

I would like to propose several improvements to the plugin, that I would find very useful and I am able to help with their development if the ideas will be accepted.

Whole proposal comes from the lack of possibility to use some basic functions related to search service in Azure Portal when search service has any firewall rules enabled. I am talking about the overview screen. Such restrictions are often required and not being able to do things like indexer reset or to see the indexation errors is very frustrating. Also there is no alternative really for that other than writing some custom tools that use search management API - which is not blocking any requests if they are coming from allowed IPs.

Stats

Service stats

New element after "Service Details" where we can show the usage of: storage, indexes, indexers, data sources, number of replicas, partitions, search units and the number of documents. Some simple table (with web view maybe) or later on with nice charts.

Indexes stats

Summary of documents count and used storage per index.

Indexers stats

Summary of indexes, status of last indexer execution, last indexer execution, docs succeeded, number of errors/warnings.

Indexer stats

For the particular indexer I would like to add the ability to be able to browse last indexer execution with details related to each execution like duration, docs succeeded, errors/warnings.

What do you think? Would I have a green light from you guys to start implementing those elements?

I'm trying to figure out how to file some issues / feature requests and can't seem to find any sources of truth in either the Azure or Microsoft orgs.

This is a great extension, but it doesn't pick up the current Azure Account environment setting, such as APIM, Function Apps, etc. In VS Code, when you are signed in with the "Azure Account" extension for Azure Government the following error occurs:

Error: The access token has been obtained for wrong audience or resource 'https://management.core.windows.net/". It should exactly match with one of the allowed audiences 'https://management.core.usgovclientapi.net"....

Does this occur consistently?
Repro steps:

Action: azureCognitiveSearch.searchDocument.onDidSaveTextDocument
Error type: Error
Error Message: Error: connect ETIMEDOUT 10.124.40.14:443

Version: 0.2.0
OS: win32
OS Release: 10.0.14393
Product: Visual Studio Code
Product Version: 1.56.2
Language: en

SimpleSearchClient.<anonymous> extension.bundle.js:5:209545
rejected extension.bundle.js:5:206203
processTicksAndRejections task_queues.js:93:5

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

👋 Hi there, Martin here, from the VS Code team.

Recently we've announced the Remote Repository feature that lets you browse and edit files and folders directly on GitHub.

Open Remote Repository... opens VSCode on a folder or workspace located on a virtual file system. We call this a virtual workspace. We observed that not all extension support this well, either because they can not, or they haven't thought about it.

It would be fantastic if you could test whether your extension can handle virtual workspaces:

Check out the Virtual Workspaces Extension Author Guide on how to do that.

When done, set the new virtualWorkspaces capability in your 'package.json'.

{
  "capabilities": {
    "virtualWorkspaces": true | false
  }
}

• Use "virtualWorkspaces": true if your extension is prepared for virtual workspaces
• Use "virtualWorkspaces": false if your extension should be disabled when a virtual workspace is opened

For questions and comments please use the Virtual Workspaces Tracking Issue.

Thanks for the support and the great work! ❤️