Skip to content

The chosen projet environnement is no longer activated in the controller #128

Closed

Description

@franckgaga

Hello,

This issue is related to #28. Starting from Julia Extension v1.250.2, the selected project environment in VS Code, here:

Image

is no longer activated in the test item controller process. This is also the activated environment the builtin VS Code REPL:

Image

My TestMPC environment include a LocalPreferences.toml file to skip the precompilation of my package. Thus, I'm no longer able to skip the precompilation of my package.

We can see in the test item controller log that both the package URI and project URI correspond to the path of my deved package:

┌ Info: Test environment
│ 
│ Project Uri: file:///c%3A/Users/francis.gagnon/.julia/dev/ModelPredictiveControl
│ Package Uri: file:///c%3A/Users/francis.gagnon/.julia/dev/ModelPredictiveControl
│ Package Name: ModelPredictiveControl
│ Julia command: C:\Users\francis.gagnon\.julia\juliaup\julia-1.13.3+0.x64.w64.mingw32\bin\julia.exe
│ Julia args: String[]
│ Julia Num Threads: auto
│ Mode: Normal
│ Env:
│ 
│ 
└ We need 1 procs, there are 0 processes, of which 0 are idle.

The project Uri should be the path of my TestMPC project environment.

Activity

  1. franckgaga commented on Oct 26, 2026

    @franckgaga
    Author

    Hum false alarm. I tried to revert to an older Julia extension version and I had the same issue. So I just deleted my manifest files everywhere, re-instantiated, and now the issue is solved, both on v1.238.2 and v1.250.2:

    ┌ Info: Test environment
    │ 
    │ Project Uri: file:///c%3A/Users/francis.gagnon/Dropbox/Programmation/Julia/TestMPC
    │ Package Uri: file:///c%3A/Users/francis.gagnon/.julia/dev/ModelPredictiveControl
    │ Package Name: ModelPredictiveControl
    │ Julia command: C:\Users\francis.gagnon\.julia\juliaup\julia-1.13.3+0.x64.w64.mingw32\bin\julia.exe
    │ Julia args: String[]
    │ Julia Num Threads: auto
    │ Mode: Normal
    │ Env:
    │ 
    │ 
    └ We need 1 procs, there are 0 processes, of which 0 are idle.

    Note sure what was the real root cause, but I will close the issue. Sorry for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions