Matthew Fisher

**Informational summary**: 1) User has found a potential bug issue in the Extension view 2) One of our team members identified it as an external / upstream issue 3) Original...

Another quick update, talked with Isidor and it looks like this will be investigated further in the November milestone for VS Code

Upstream issue being tracked against has been closed, can you please reconfirm to see if we can have this issue closed as well @12-shweta. Thank you!

For tracking purposes, comment by Isidor in [#149305](https://github.com/microsoft/vscode/issues/149305) indicates that the best issue to track against for this one is [#133169](https://github.com/microsoft/vscode/issues/133169). There was mention that the severity of the issue...

Relevant comment [here](https://github.com/microsoft/vscode/issues/133169#issuecomment-1275639912) and [here](https://github.com/microsoft/vscode/issues/133169#issuecomment-1284812345) related to this issue.

Update: This [comment](https://github.com/microsoft/vscode-azurefunctions/issues/2942#issuecomment-1289787198) applies here as well, same upstream tracking.

Does this only reproduce when you're running WSL Ubuntu?

To mitigate this, we can skip throwing the error when `AzureWebJobsStorage` is missing but we are able to detect `AzureWebJobsStorage__accountName`

We may need to update the `host.json` configuration for `Intellisense` to recognize these properties https://github.com/SchemaStore/schemastore

Alex may have already addressed this issue