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

Once onInterpretersChanged event is exposed via API, revisit whether discovery can be triggered after activation #17498

Closed
karrtikr opened this issue Sep 22, 2021 · 1 comment
Assignees
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality

Comments

@karrtikr
Copy link

karrtikr commented Sep 22, 2021

See #17499

@karrtikr karrtikr added feature-request Request for new features or functionality needs PR area-environments Features relating to handling interpreter environments labels Sep 22, 2021
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 22, 2021
@karrtikr karrtikr removed the triage-needed Needs assignment to the proper sub-team label Sep 22, 2021
@karrtikr karrtikr self-assigned this May 13, 2022
@karrtikr
Copy link
Author

karrtikr commented May 13, 2022

Closing in favor of #19102. This won't be that much of a problem if discovery is only triggered once, and not every session.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

1 participant