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

Switching to an environment works differently in different situations #3591

Open
PetrKryslUCSD opened this issue Apr 22, 2024 · 1 comment
Open
Labels

Comments

@PetrKryslUCSD
Copy link

PetrKryslUCSD commented Apr 22, 2024

Something doesn't quite work in VSCode with the environments. I set up an environment for examples and I run activate and instantiate in that folder, and it looks like this:
image
So the environment is correctly recognized (according to the bottom line in the editor), yet the symbols of FinEtoolsDeforLinear are not recognized. Others are, such as LinearAlgebra and so on.

On the other hand, if I open the examples folder Using the command File: Open Folder, at first sight everything looks identical (the environment at the bottom)
image
but something is different because now the symbols from FinEtoolsDeforLinear are recognized no problem (the hover gives documentation hints and so forth).

Finally, I explicitly select the examples environment (and the status bar at the bottom looks the same as above), yet the symbols from FinEtoolsDeforLinear are again not recognized.

This is with
Version: 1.88.1
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:41:02.734Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631
And the julia extension is v1.76.2.

@pfitzseb pfitzseb added the bug label Apr 23, 2024
@j-adel
Copy link

j-adel commented May 18, 2024

I've also recently encountered this issue as well.
It's very strange but for some reason just transplanting the code from a malfunctioning environment to another working one would make it work just fine. Is there a way to clear the cache for a working directory for the linter to try again checking the dependencies and hopefully fix itself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants