Skip to content
New issue

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

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

Already on GitHub? # to your account

Variables Pane Interpreter Selector Out of Sync with Others #6355

Closed
samclark2015 opened this issue Feb 14, 2025 · 3 comments
Closed

Variables Pane Interpreter Selector Out of Sync with Others #6355

samclark2015 opened this issue Feb 14, 2025 · 3 comments

Comments

@samclark2015
Copy link
Contributor

If multiple versions of a language have been utilized in a session, the variables pane continues to show inactive versions of the runtime.

Image

In image above, Python 3.12 was initially activated and then switched to Python 3.11. As seen, Python 3.12 still appears.

Attempting to switch to an inactive interpreter version within the variables pane updates the top-bar interpreter dropdown; the console and variables pane selectors both stay on the current, running interpreter version. Additionally, duplicate entries for the same runtime version may appear under the variables pane selector.

Screen.Recording.2025-02-13.at.3.25.00.PM.mov

Similarly, if the kernel is changed in a Notebook file, duplicate Notebook runtime entries appear in the runtime select in the variables pane.

System details:

Positron and OS details:

Positron Dev Version: 2025.03.0 build 0
Code - OSS Version: 1.96.0
Commit: Unknown
Date: Unknown
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

Interpreter details:

Python 3.11.11
Python 3.12.8
R 4.4.0

Describe the issue:

See Above

Steps to reproduce the issue:

  1. Start/activate Python (or R?) interpreter using top-bar interpreter drop down.
  2. Start new interpreter using a different version of the same language.
  3. Variables pane now shows both versions of the language in its selector. The originally activated runtime is broken.

Expected or desired behavior:

Interpreter options offered by the variables pane match what is active & available in the Console pane and main Interpreter dropdown.

Were there any error messages in the UI, Output panel, or Developer Tools console?

None

@samclark2015 samclark2015 added this to the Release Candidate milestone Feb 14, 2025
@jmcphers
Copy link
Collaborator

Is this the same as #3504?

@ntluong95
Copy link

It is a persistent bug. The unused/inactive runtime should be removed from the list

@samclark2015
Copy link
Contributor Author

@jmcphers Yes - same thing. Apologies for the dupe!

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

No branches or pull requests

3 participants