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

Starting and stopping runtimes in the TopActionBarInterpretersManager component results in incorrect runtimes being displayed in the VariablesInstanceMenuButton component #6029

Open
softwarenerd opened this issue Jan 16, 2025 · 1 comment
Assignees
Labels
area: top bar Issues related to Top Bar category. area: variables Issues related to Variables category. bug Something isn't working

Comments

@softwarenerd
Copy link
Contributor

softwarenerd commented Jan 16, 2025

Starting and stopping runtimes in the TopActionBarInterpretersManager component results in the VariablesInstanceMenuButton displaying runtimes that are no longer running:

Image

In this example, I started and stopped Python 3.11.9 and 3.12.4 a number of times. The VariablesInstanceMenuButton should look like the console:

Image

@softwarenerd softwarenerd self-assigned this Jan 16, 2025
@softwarenerd softwarenerd changed the title Starting and stopping runtimes results in incorrect runtimes being displayed in the VariablesInstanceMenuButton component Starting and stopping runtimes results in incorrect runtimes being displayed in the VariablesInstanceMenuButton component Jan 16, 2025
@softwarenerd softwarenerd added bug Something isn't working area: top bar Issues related to Top Bar category. area: variables Issues related to Variables category. area: runtimes Issues related to Language Runtimes and removed area: runtimes Issues related to Language Runtimes labels Jan 16, 2025
@softwarenerd softwarenerd added this to the 2025.02.0 Pre-Release milestone Jan 16, 2025
@softwarenerd softwarenerd changed the title Starting and stopping runtimes results in incorrect runtimes being displayed in the VariablesInstanceMenuButton component Starting and stopping runtimes in the TopActionBarInterpretersManager component results in incorrect runtimes being displayed in the VariablesInstanceMenuButton component Jan 16, 2025
@jmcphers
Copy link
Collaborator

My recollection is that we did this intentionally to make it less jarring when your runtime exits -- your variables just get disabled instead of flashing out of existence. But maybe that's better than this experience? (Or we could leave the variables disabled and then just discard them when you switch away?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: top bar Issues related to Top Bar category. area: variables Issues related to Variables category. bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants