Skip to content

Conversation

@karthiknadig
Copy link
Member

fixes: #383

The fix is to trigger FS event on activate file creation. This makes sure that we have the right files available for the environment.

@karthiknadig karthiknadig requested a review from anthonykim1 May 5, 2025 20:44
@karthiknadig karthiknadig self-assigned this May 5, 2025
@karthiknadig karthiknadig added the bug Issue identified by VS Code Team member as probable bug label May 5, 2025
@karthiknadig karthiknadig marked this pull request as ready for review May 5, 2025 20:51
@vs-code-engineering
Copy link

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

@vs-code-engineering vs-code-engineering bot added this to the May 2025 milestone May 5, 2025
@karthiknadig karthiknadig merged commit a2abdfb into microsoft:main May 5, 2025
6 checks passed
@karthiknadig karthiknadig deleted the fix-env-bug branch May 5, 2025 21:02
NguyenCuong1989 referenced this pull request in NguyenCuong1989/vscode-python-environments Oct 23, 2025
…384)

fixes:
microsoft/vscode-python-environments#383

The fix is to trigger FS event on `activate` file creation. This makes
sure that we have the right files available for the environment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Broken activate contribution when creating virtual environment from terminal

2 participants