Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lost intellisense #2146

Closed
rajesh-chawla opened this issue Nov 12, 2019 · 7 comments
Closed

Lost intellisense #2146

rajesh-chawla opened this issue Nov 12, 2019 · 7 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@rajesh-chawla
Copy link

Unfortunately, I've lost intellisense when I code in the container. How can I go about troubleshooting this? So far, I've tried reopening the container as well as rebuilding it.

Any pointers would be appreciated.

@deinman
Copy link

deinman commented Jan 9, 2020

I've had this issue as well. Looks to be an issue with the C# extension getting installed in the container. A workaround is to open your VS Code Extensions menu, search for the C# extension, click "Install in Dev Container", then reload the container. If I figure out how to get it working with the devcontainer.json extension again I'll let you know!

@Chuxel
Copy link
Member

Chuxel commented Jan 9, 2020

@deinman Are you finding this happen consistently? If so, it could be some sort of product issue. Moving this to the vscode-remote-release repo.

If you see it again, could you capture the logs when the container is created? (Located in the contents of the "Dev Containers" terminal window.)

@Chuxel Chuxel transferred this issue from microsoft/vscode-remote-try-dotnet Jan 9, 2020
@deinman
Copy link

deinman commented Jan 10, 2020

Yes, I've seen this on both machines I've run it on here. Here's the logs including the complete container rebuild:

20200110_devContainerLogs.txt

Looking at the log it looks to be an issue with my network's HTTPS cert injection causing the container to not be able to get the local issuer cert.

Line 292: unable to get local issuer certificate

Is there maybe a flag that I could set somewhere to allow insecure certs? For what it's worth, using the UI to add the extension does work, so it stands to reason I should be able to get the container to do it.

@Chuxel
Copy link
Member

Chuxel commented Jan 10, 2020

//cc: @chrmarti Any idea why this would be happening on container create but not via the UI? It's the same acquisition code path, correct?

@chrmarti
Copy link
Contributor

I think there is a fallback when going through the UI that will use the Chromium network stack on the UI-side to get the extension when getting it on the remote side failed. /cc @sandy081

@roblourens roblourens assigned sandy081 and chrmarti and unassigned sandy081 Feb 3, 2020
@chrmarti
Copy link
Contributor

chrmarti commented Feb 4, 2020

/duplicate #986

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 4, 2020
@vscodebot
Copy link

vscodebot bot commented Feb 4, 2020

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Feb 4, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

5 participants