Use worker threads for launching conda and windows registry when discovering #22146
Assignees
Labels
area-environments
Features relating to handling interpreter environments
feature-request
Request for new features or functionality
needs PR
Ready to be worked on
verification-needed
Verification of issue is requested
verified
Verification succeeded
Milestone
Comments
karrtikr
added
feature-request
This was referenced Oct 6, 2023
29 tasks
karrtikr
changed the title
This was referenced Nov 15, 2023
|
@deepak1556 do you know why spawn would be blocking the thread for so long here?
Profiles at #21755 (comment) |
|
Note this is when spawning the conda binary, similarly spawning REG binaries can seldomly be like this. But python binaries are much cheaper for some reason. |
karrtikr
pushed a commit
that referenced
this issue
Nov 16, 2023
|
It's not just us, the git extension while spawning also runs into this:
|
This was my observation a few years ago as well ( #15813 (comment)) |
3 tasks
|
Performance issue filled for other cases here: microsoft/vscode#198384 |
|
Yeah a few ms is expected, but it's very different from over 2 seconds which is what the first spawn takes in my screenshot. |
|
@Tyriar not sure but having some basic data points from @karrtikr I feel there is a binary scanning delaying the spawn call. @karrtikr can you collect an event trace following the steps below.
|
|
I've shared the event trace via email. |
This was referenced Nov 21, 2023
|
@karrtikr thanks for the trace, I looked into it and found it to be unusual, the Can you provide me another windows event trace of the slow conda or win reg or git spawn calls but this time don't invoke the v8 cpu profiler. I am curious to see how the trace comes out without any node inspector involved. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Issue is unrelated to the node.js issue, it is specific to fork syscall on linux impacted with v8 heap regions which is already fixed in upstream and also fixed in our stable versions for a while now. I haven't seen similar issues for windows and the current data is still too early to conclude. |
rzhao271
removed
verified
|
@andreamah I've prepared a fix which very likely fixes the issue, please give it a try when you can: https://github.com/microsoft/vscode-python/actions/runs/8045205090/artifacts/1274325464. You can use Make sure run |
|
@andreamah Fix should be out in the pre-release version of the extension. |
anthonykim1
pushed a commit
that referenced
this issue
Feb 29, 2024
|
Verification steps: #22146 (comment) |
|
This failed verification for me, the output shows the worker option is active, but there's an exception launching conda (which I don't think is installed) and there's no "worker id": |
Sorry, this is actually expected, missed to update the verification steps from before. The important thing to verify here is that the number of environments discovered are still the same, once discovery finishes in both cases. |
karrtikr
added
verified
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Mar 28, 2024
…from upstream Merge pull request #277 from posit-dev/merge/2023.22 Merge vscode-python 2023.22 from upstream -------------------- Commit message for posit-dev/positron-python@2e3ea32: handle new upstream `deprecated` response upon parser error -------------------- Commit message for posit-dev/positron-python@d50c326: Update yarn.lock -------------------- Commit message for posit-dev/positron-python@105bf9d: Merge commit 'a0cddbdf0939729cdb82dca2d129433ad475f51e' -------------------- Commit message for microsoft/vscode-python@a0cddbd: bump-release-2023.22 (microsoft/vscode-python#22587) bump to release version 2023.22 and update package.json -------------------- Commit message for microsoft/vscode-python@5302d0e: Revert unsuccessful REPL decoration fix and disable for windows (microsoft/vscode-python#22578) Reverting microsoft/vscode-python#22572 since it is producing color decoration on weird Python REPL spot for Windows pwsh users, and disable decoration entirely for Windows pwsh users temporarily while trying to fix specific problem. Disable feature for stable. Refer: microsoft/vscode-python#22546 microsoft/vscode-python#22535 -------------------- Commit message for microsoft/vscode-python@bffc9b3: Fix shell integration decoration bug for Windows pwsh (microsoft/vscode-python#22572) Attempt to fix colorless and randomized circle decoration for Python REPL usage by Windows Powershell users. Resolves: microsoft/vscode-python#22546 microsoft/vscode-python#22535 -------------------- Commit message for microsoft/vscode-python@e1b54d0: fix no test id provided for pytest run (microsoft/vscode-python#22569) fixes microsoft/vscode-python#22567 Now if a user tries to click the "run" button a empty folder (ie a folder with no tests in it) it will just run pytest with no testIds as args and notify the user. -------------------- Commit message for microsoft/vscode-python@61fcf3a: Properly build deactivate commands for powershell (microsoft/vscode-python#22570) For microsoft/vscode-python#20950 -------------------- Commit message for microsoft/vscode-python@db6e15e: Do not throw if initializing deactivate script fails (microsoft/vscode-python#22566) For microsoft/vscode-python#20950 -------------------- Commit message for microsoft/vscode-python@caa50dc: Fix shell integration decoration for windows pwsh (microsoft/vscode-python#22560) Attempting to fix shell integration decoration glitch for windows pwsh when using Python REPL from VS Code. Resolves: microsoft/vscode-python#22546 microsoft/vscode-python#22535 -------------------- Commit message for microsoft/vscode-python@3efb54f: White space after REPL prompt (microsoft/vscode-python#22549) There should be white space after new REPL prompt that I override for purpose of shell integration. Resolves: microsoft/vscode-python#22548 -------------------- Commit message for microsoft/vscode-python@261ae66: Improvement: Pass along python interpreter to jedi-language-server (microsoft/vscode-python#22466) Fixes microsoft/vscode-python#22495 ## Before this PR Overriding the Python interpreter to a different environment that isn't the current globally-activated base environment would yield no completions when Jedi is used as the underlying language server. Example [stackoverflow question](https://stackoverflow.com/questions/62018436/vscode-intellisense-code-completion-doesnt-work-when-i-am-not-in-base-conda-e) hitting the same issue. ## After this PR We now pass along the interpreter path to jedi-language-server as part of the initial options under `workspace.environmentPath` ([ref](https://github.com/pappasam/jedi-language-server/#workspaceenvironmentpath)) -------------------- Commit message for microsoft/vscode-python@1639753: switch to conditional error message on check for UUID and port during pytest config (microsoft/vscode-python#22534) fixes microsoft/vscode-python#19857 -------------------- Commit message for microsoft/vscode-python@9a5363c: Resolve test suite discovery import errors due to path ordering (microsoft/vscode-python#22454) [Issue microsoft/vscode-python#22453](microsoft/vscode-python#22453) - Once starting to run discovery, add the projects root path to PATH at index 0 so that any further imports will use the projects root directory and not reference the incorrect directory. - Since the test suite only allows the start_dir to be one directory deep, we can conclude that if the start_dir is not "." or contains a "/", that we need to add that start_dir's parent to PATH. Otherwise, we simply add the start_dir to PATH. -------------------- Commit message for microsoft/vscode-python@eb96141: Use shell integration to denote success/failure (microsoft/vscode-python#22487) Resolves: microsoft/vscode-python#22486 Use shell integration to denote success/failure in Python REPL launched from VS Code. This would mean having the blue or red decorators based on whether or not user's command succeeded. -------------------- Commit message for microsoft/vscode-python@f6e1338: Use worker threads for fetching conda environments and interpreter related info (microsoft/vscode-python#22481) -------------------- Commit message for microsoft/vscode-python@3c552f9: Show warning and allow user to turn off smart send for deprecated Python code (microsoft/vscode-python#22353) Resolves: microsoft/vscode-python#22341 microsoft/vscode-python#22340 Showing warning message after detecting user is on Python file with deprecated Python code, and are attempting to run smart send via shift+enter action. Allow user to turn off this via workspace setting. --------- Co-authored-by: Courtney Webster <[email protected]> Co-authored-by: Kartik Raj <[email protected]> -------------------- Commit message for microsoft/vscode-python@ef983f4: Bump `vscode-tas-client` and fix tests (microsoft/vscode-python#22493) Closes microsoft/vscode-python#22461 Sinon requires the actual object definition, so we need to point it to the module file that actually has the function. -------------------- Commit message for microsoft/vscode-python@9298b2c: Bump dessant/lock-threads from 4 to 5 (microsoft/vscode-python#22474) Bumps [dessant/lock-threads](https://github.com/dessant/lock-threads) from 4 to 5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dessant/lock-threads/releases">dessant/lock-threads's releases</a>.</em></p> <blockquote> <h2>v5.0.0</h2> <p>Learn more about this release from the <a href="https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md#changelog">changelog</a>.</p> <h2>v4.0.1</h2> <p>Learn more about this release from the <a href="https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md#changelog">changelog</a>.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md">dessant/lock-threads's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/dessant/lock-threads/compare/v4.0.1...v5.0.0">5.0.0</a> (2023-11-14)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>Discussions are also processed by default, set the <code>process-only</code> input parameter to preserve the old behavior</li> </ul> <pre lang="yaml"><code> steps: - uses: dessant/lock-threads@v5 with: process-only: 'issues, prs' </code></pre> <ul> <li>the action now requires Node.js 20</li> </ul> <h3>Features</h3> <ul> <li>lock discussions (<a href="https://github.com/dessant/lock-threads/commit/0a0976f3ded51c88c6128dd96dd115c9f14fa764">0a0976f</a>), closes <a href="https://redirect.github.com/dessant/lock-threads/issues/25">#25</a></li> </ul> <h3>Bug Fixes</h3> <ul> <li>update dependencies (<a href="https://github.com/dessant/lock-threads/commit/5a25b54eae3e7a5580d09ef0f7cbc5b18376db67">5a25b54</a>)</li> </ul> <h3><a href="https://github.com/dessant/lock-threads/compare/v4.0.0...v4.0.1">4.0.1</a> (2023-06-12)</h3> <h3>Bug Fixes</h3> <ul> <li>retry and throttle GitHub API requests (<a href="https://github.com/dessant/lock-threads/commit/1618e91da69b9fe614fb9837ac673ea4600eb529">1618e91</a>), closes <a href="https://redirect.github.com/dessant/lock-threads/issues/35">#35</a></li> </ul> <h2><a href="https://github.com/dessant/lock-threads/compare/v3.0.0...v4.0.0">4.0.0</a> (2022-12-04)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>the action now requires Node.js 16</li> </ul> <h3>Bug Fixes</h3> <ul> <li>update dependencies (<a href="https://github.com/dessant/lock-threads/commit/38e918558115222435d26c0639870cdbe3572929">38e9185</a>)</li> <li>update docs (<a href="https://github.com/dessant/lock-threads/commit/32986e26965060a85db09e98ef7e5958c961ae84">32986e2</a>)</li> </ul> <h2><a href="https://github.com/dessant/lock-threads/compare/v2.1.2...v3.0.0">3.0.0</a> (2021-09-27)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>input parameter names have changed</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dessant/lock-threads/commit/d42e5f49803f3c4e14ffee0378e31481265dda22"><code>d42e5f4</code></a> chore(release): 5.0.0</li> <li><a href="https://github.com/dessant/lock-threads/commit/d8da6c1485cbe748b5b632f1a52cf2a52941cbf9"><code>d8da6c1</code></a> chore: update package</li> <li><a href="https://github.com/dessant/lock-threads/commit/c1eab4b45f97073a922fbd226afab0e34a70cf5f"><code>c1eab4b</code></a> chore: update workflow</li> <li><a href="https://github.com/dessant/lock-threads/commit/0a0976f3ded51c88c6128dd96dd115c9f14fa764"><code>0a0976f</code></a> feat: lock discussions</li> <li><a href="https://github.com/dessant/lock-threads/commit/53f3f0c0b9158bece84746885adc5f4bf2dd1ddc"><code>53f3f0c</code></a> chore: migrate package to ESM</li> <li><a href="https://github.com/dessant/lock-threads/commit/5a25b54eae3e7a5580d09ef0f7cbc5b18376db67"><code>5a25b54</code></a> fix: update dependencies</li> <li>See full diff in <a href="https://github.com/dessant/lock-threads/compare/v4...v5">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for microsoft/vscode-python@e27185a: Use worker threads for fetching Windows Registry interpreters (microsoft/vscode-python#22479) For microsoft/vscode-python#22146 -------------------- Commit message for microsoft/vscode-python@7a4de92: Use `WorkspaceFolder.name` in addition to workspace folder's basename when resolving `${workspaceFolder:name}` syntax in settings (microsoft/vscode-python#22471) Closes microsoft/vscode-python#22452 -------------------- Commit message for microsoft/vscode-python@fbfa126: Add 3.12 to conda version list (microsoft/vscode-python#22470) -------------------- Commit message for microsoft/vscode-python@47552a3: Install requirements before toml (microsoft/vscode-python#22468) Fixes microsoft/vscode-python#22423 -------------------- Commit message for microsoft/vscode-python@a1fac81: If active editor opened is outside the editor, activate the first workspace (microsoft/vscode-python#22450) For microsoft/vscode-python#22449 -------------------- Commit message for microsoft/vscode-python@b68ddee: Support deactivating virtual environments without user intervention (microsoft/vscode-python#22405) Closes microsoft/vscode-python#22448 Adds deactivate script to `PATH` -------------------- Commit message for microsoft/vscode-python@8d174a8: Fix shell integration API reliability (microsoft/vscode-python#22446) microsoft/vscode-python#22440 It leads to terminals activating forever. -------------------- Commit message for microsoft/vscode-python@1b3c1ea: Adding `Locked` comments to walkthrough commands (microsoft/vscode-python#22432) Adds comments to lock command names for walkthrough localization. Only added Locked comments for walkthrough tiles that are in use and have commands -------------------- Commit message for microsoft/vscode-python@2fc9fea: Revert "Reliably detect whether shell integration is working" (microsoft/vscode-python#22445) Reverts microsoft/vscode-python#22440 It seems reactivating never finishes after this, although this doesn't repro when debugging the extension, have to investigate further. -------------------- Commit message for microsoft/vscode-python@f98caf6: Add consoleTitle to launch.json properties schema (microsoft/vscode-python#22406) consoleTitle is effectively an undocumented feature. pydebug accepts the config key, but vscode will report a problem because it is missing from the schema. see [this debugpy issue](microsoft/debugpy#1178) and [#13040](microsoft/vscode-python#13040) I used the phrase "console or terminal" because I noticed the name was represented on both integratedTerminal and internalConsole. I didn't test externalTerminal. --------- Co-authored-by: Luciana Abud <[email protected]> -------------------- Commit message for microsoft/vscode-python@2a976e3: Reliably detect whether shell integration is working (microsoft/vscode-python#22440) Closes microsoft/vscode-python#22439 Blocked on https://github.com/microsoft/vscode-distro/pull/822 -------------------- Commit message for microsoft/vscode-python@67b4801: Improve shell identifier on case-insensitive system (microsoft/vscode-python#22391) Use case-insensitive regex to remove `.exe` extension. See: microsoft/vscode-python#22036 (comment) -------------------- Commit message for microsoft/vscode-python@7bc45e5: Do not attempt to kill the process if it has already exited (microsoft/vscode-python#22424) Closes microsoft/vscode-python#22420 This bugs seems to have existed every since `rawProcessApi.ts` was created. `proc.killed` can be `false` even after process has exited. -------------------- Commit message for microsoft/vscode-python@f6cfa6e: Remove old code for folder support in interpreter path setting (microsoft/vscode-python#22413) Closes microsoft/vscode-python#12452 Lead-authored-by: Kartik Raj <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Courtney Webster <[email protected]> Co-authored-by: John H. Ayad <[email protected]> Co-authored-by: Wasim Lorgat <[email protected]> Co-authored-by: Shane Saravia <[email protected]> Co-authored-by: Trysten <[email protected]> Co-authored-by: JamzumSum <[email protected]> Co-authored-by: Eleanor Boyd <[email protected]> Co-authored-by: Karthik Nadig <[email protected]> Co-authored-by: Pete Farland <[email protected]> Co-authored-by: Anthony Kim <[email protected]> Signed-off-by: GitHub <[email protected]>
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Mar 28, 2024
Merge pull request #395 from posit-dev/merge/v2024.2.0 Merge upstream: `v2024.2.0` -------------------- Commit message for posit-dev/positron-python@7d85a51: ignore pyright errors in ms testing files -------------------- Commit message for posit-dev/positron-python@f9a3259: Bump flask from 3.0.1 to 3.0.2 (posit-dev/positron-python#354) Bumps [flask](https://github.com/pallets/flask) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/pallets/flask/releases) - [Changelog](https://github.com/pallets/flask/blob/main/CHANGES.rst) - [Commits](pallets/flask@3.0.1...3.0.2) --- updated-dependencies: - dependency-name: flask dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@ea812a4: Bump ipywidgets from 8.1.1 to 8.1.2 (posit-dev/positron-python#368) Bumps [ipywidgets](https://github.com/jupyter-widgets/ipywidgets) from 8.1.1 to 8.1.2. - [Release notes](https://github.com/jupyter-widgets/ipywidgets/releases) - [Commits](jupyter-widgets/ipywidgets@8.1.1...8.1.2) --- updated-dependencies: - dependency-name: ipywidgets dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Isabel Zimmerman <[email protected]> -------------------- Commit message for posit-dev/positron-python@e3a5399: Bump pyright from 1.1.349 to 1.1.351 (posit-dev/positron-python#379) Bumps [pyright](https://github.com/RobertCraigie/pyright-python) from 1.1.349 to 1.1.351. - [Release notes](https://github.com/RobertCraigie/pyright-python/releases) - [Commits](RobertCraigie/pyright-python@v1.1.349...v1.1.351) --- updated-dependencies: - dependency-name: pyright dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@2eeb677: Bump polars from 0.20.6 to 0.20.11 (posit-dev/positron-python#394) Bumps [polars](https://github.com/pola-rs/polars) from 0.20.6 to 0.20.11. - [Release notes](https://github.com/pola-rs/polars/releases) - [Commits](pola-rs/polars@py-0.20.6...py-0.20.11) --- updated-dependencies: - dependency-name: polars dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@573d9fd: Bump ipykernel from 6.29.0 to 6.29.3 (posit-dev/positron-python#390) Bumps [ipykernel](https://github.com/ipython/ipykernel) from 6.29.0 to 6.29.3. - [Release notes](https://github.com/ipython/ipykernel/releases) - [Changelog](https://github.com/ipython/ipykernel/blob/main/CHANGELOG.md) - [Commits](ipython/ipykernel@v6.29.0...v6.29.3) --- updated-dependencies: - dependency-name: ipykernel dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@334b383: update package.json -------------------- Commit message for posit-dev/positron-python@7ce08b1: Merge tag 'v2024.2.0' into merge/v2024.2.0 -------------------- Commit message for posit-dev/positron-python@063ba15: Finalized-release-2024.2.0 (posit-dev/positron-python#22996) Finalized release 2024.2.0: removing -rc -------------------- Commit message for posit-dev/positron-python@3eef025: Bump release 2024.2 (posit-dev/positron-python#22972) Bump release 2024.2 -------------------- Commit message for posit-dev/positron-python@1fbd77b: skip tests, pytest upstream regression (posit-dev/positron-python#22974) Short-term fix to stop CI from failing due to a regression upstream from pytest. See issue for details: microsoft/vscode-python#22965. -------------------- Commit message for microsoft/vscode-python@4fca030: Adding GDPR tag for isFirstSession (microsoft/vscode-python#22955) -------------------- Commit message for microsoft/vscode-python@ba94553: Modify telemetry to contain trigger time as property (microsoft/vscode-python#22941) -------------------- Commit message for microsoft/vscode-python@178a0b2: Fix bug with symlink for pytest execution (microsoft/vscode-python#22952) Fixes microsoft/vscode-python#22938 -------------------- Commit message for microsoft/vscode-python@bae7d40: Update vscode-tas-client version (microsoft/vscode-python#22876) -------------------- Commit message for microsoft/vscode-python@75ed73e: Fix Bug with Pytest when using symlinked workspaces (microsoft/vscode-python#22885) fixes microsoft/vscode-python#22658 also implements switching to arg mapping which is this issue here: microsoft/vscode-python#22076 --------- Co-authored-by: Karthik Nadig <[email protected]> -------------------- Commit message for microsoft/vscode-python@e53651d: Prevent first Python command being lost (microsoft/vscode-python#22902) Fixes: microsoft/vscode-python#22673 Fixes: microsoft/vscode-python#22545 Fixes: microsoft/vscode-python#22691 Making best effort to address issue where very first command sent to REPL via Terminal gets ignored, or gets pasted both in Terminal and in REPL. With the fix, we observe whether Python REPL is launched in Terminal via VS Code's `onDidWriteTerminalData` and send the command, or wait three seconds as a fallback mechanism. These two combined together will significantly reduce or resolve all-together the chance of very first command being swollen up or gets pasted twice in Terminal and REPL previously where it did not have context of whether Python REPL instance have started inside the Terminal or not. -------------------- Commit message for microsoft/vscode-python@a60fbd5: Add GDPR tags for new Pylance properties (microsoft/vscode-python#22922) -------------------- Commit message for microsoft/vscode-python@aff0b05: Use python debugger in testing (microsoft/vscode-python#22903) closed: microsoft/vscode-python-debugger#174 -------------------- Commit message for microsoft/vscode-python@84734a8: Updating installed extensions section of README.md (microsoft/vscode-python#22893) Adding the Python Debugger to the installed extensions section of the README. -------------------- Commit message for microsoft/vscode-python@2159238: Bump actions/setup-python from 4 to 5 in /.github/actions/build-vsix (microsoft/vscode-python#22602) Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/setup-python/releases">actions/setup-python's releases</a>.</em></p> <blockquote> <h2>v5.0.0</h2> <h2>What's Changed</h2> <p>In scope of this release, we update node version runtime from node16 to node20 (<a href="https://redirect.github.com/actions/setup-python/pull/772">actions/setup-python#772</a>). Besides, we update dependencies to the latest versions.</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-python/compare/v4.8.0...v5.0.0">https://github.com/actions/setup-python/compare/v4.8.0...v5.0.0</a></p> <h2>v4.8.0</h2> <h2>What's Changed</h2> <p>In scope of this release we added support for GraalPy (<a href="https://redirect.github.com/actions/setup-python/pull/694">actions/setup-python#694</a>). You can use this snippet to set up GraalPy:</p> <pre lang="yaml"><code>steps: - uses: actions/checkout@v4 - uses: actions/setup-python@v4 with: python-version: 'graalpy-22.3' - run: python my_script.py </code></pre> <p>Besides, the release contains such changes as:</p> <ul> <li>Trim python version when reading from file by <a href="https://github.com/FerranPares"><code>@FerranPares</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/628">actions/setup-python#628</a></li> <li>Use non-deprecated versions in examples by <a href="https://github.com/jeffwidman"><code>@jeffwidman</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/724">actions/setup-python#724</a></li> <li>Change deprecation comment to past tense by <a href="https://github.com/jeffwidman"><code>@jeffwidman</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/723">actions/setup-python#723</a></li> <li>Bump <code>@babel/traverse</code> from 7.9.0 to 7.23.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/743">actions/setup-python#743</a></li> <li>advanced-usage.md: Encourage the use actions/checkout@v4 by <a href="https://github.com/cclauss"><code>@cclauss</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/729">actions/setup-python#729</a></li> <li>Examples now use checkout@v4 by <a href="https://github.com/simonw"><code>@simonw</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/738">actions/setup-python#738</a></li> <li>Update actions/checkout to v4 by <a href="https://github.com/dmitry-shibanov"><code>@dmitry-shibanov</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/761">actions/setup-python#761</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/FerranPares"><code>@FerranPares</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-python/pull/628">actions/setup-python#628</a></li> <li><a href="https://github.com/timfel"><code>@timfel</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-python/pull/694">actions/setup-python#694</a></li> <li><a href="https://github.com/jeffwidman"><code>@jeffwidman</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-python/pull/724">actions/setup-python#724</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-python/compare/v4...v4.8.0">https://github.com/actions/setup-python/compare/v4...v4.8.0</a></p> <h2>v4.7.1</h2> <h2>What's Changed</h2> <ul> <li>Bump word-wrap from 1.2.3 to 1.2.4 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/702">actions/setup-python#702</a></li> <li>Add range validation for toml files by <a href="https://github.com/dmitry-shibanov"><code>@dmitry-shibanov</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/726">actions/setup-python#726</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-python/compare/v4...v4.7.1">https://github.com/actions/setup-python/compare/v4...v4.7.1</a></p> <h2>v4.7.0</h2> <p>In scope of this release, the support for reading python version from pyproject.toml was added (<a href="https://redirect.github.com/actions/setup-python/pull/669">actions/setup-python#669</a>).</p> <pre lang="yaml"><code> - name: Setup Python uses: actions/setup-python@v4 </tr></table> </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/setup-python/commit/0a5c61591373683505ea898e09a3ea4f39ef2b9c"><code>0a5c615</code></a> Update action to node20 (<a href="https://redirect.github.com/actions/setup-python/issues/772">#772</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/0ae58361cdfd39e2950bed97a1e26aa20c3d8955"><code>0ae5836</code></a> Add example of GraalPy to docs (<a href="https://redirect.github.com/actions/setup-python/issues/773">#773</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/b64ffcaf5b410884ad320a9cfac8866006a109aa"><code>b64ffca</code></a> update actions/checkout to v4 (<a href="https://redirect.github.com/actions/setup-python/issues/761">#761</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/8d2896179abf658742de432b3f203d2c2d86a587"><code>8d28961</code></a> Examples now use checkout@v4 (<a href="https://redirect.github.com/actions/setup-python/issues/738">#738</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/7bc6abb01e0555719edc2dbca70a2fde309e5e56"><code>7bc6abb</code></a> advanced-usage.md: Encourage the use actions/checkout@v4 (<a href="https://redirect.github.com/actions/setup-python/issues/729">#729</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/e8111cec9d3dc15220d8a3b638f08419f57b906a"><code>e8111ce</code></a> Bump <code>@babel/traverse</code> from 7.9.0 to 7.23.2 (<a href="https://redirect.github.com/actions/setup-python/issues/743">#743</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/a00ea43da65e7c04d2bdae58b3afecd77057eb9e"><code>a00ea43</code></a> add fix for graalpy ci (<a href="https://redirect.github.com/actions/setup-python/issues/741">#741</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/8635b1ccc5934e73ed3510980fd2e7790b85839b"><code>8635b1c</code></a> Change deprecation comment to past tense (<a href="https://redirect.github.com/actions/setup-python/issues/723">#723</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/f6cc428f535856f9c23558d01765a42a4d6cf758"><code>f6cc428</code></a> Use non-deprecated versions in examples (<a href="https://redirect.github.com/actions/setup-python/issues/724">#724</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/5f2af211d616f86005883b44826180b21abb4060"><code>5f2af21</code></a> Add GraalPy support (<a href="https://redirect.github.com/actions/setup-python/issues/694">#694</a>)</li> <li>Additional commits viewable in <a href="https://github.com/actions/setup-python/compare/v4...v5">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for microsoft/vscode-python@83cf53b: Add "isMeasurement" for LANGUAGE_SERVER_TRIGGER_DURATION (microsoft/vscode-python#22912) cc/ @cwebster-99 -------------------- Commit message for microsoft/vscode-python@7be33eb: Add more shell integration sequences to check for (microsoft/vscode-python#22911) Based on discussion with Daniel For microsoft/vscode-python#22440 -------------------- Commit message for microsoft/vscode-python@6838ccf: Do not activate microvenv if terminal.activateEnvironment is set to false and when not in terminal experiment (microsoft/vscode-python#22909) -------------------- Commit message for microsoft/vscode-python@2dc158e: Log options being passed when using environment collection APIs (microsoft/vscode-python#22907) For microsoft/vscode-python#22899 -------------------- Commit message for microsoft/vscode-python@5f971ae: Prepend `PATH` both at shell integration and process creation (microsoft/vscode-python#22905) -------------------- Commit message for microsoft/vscode-python@5174d5c: Improve shell integration reliability for zsh (microsoft/vscode-python#22891) Closes microsoft/vscode-python#22881 If status changes, re-run activation. Also persist once we know shell integration works for a shell. -------------------- Commit message for microsoft/vscode-python@b0c34e3: Add UnicodeDecodeError catching (microsoft/vscode-python#22873) Resolve `UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd0 in position 48995: unexpected end of data` Co-authored-by: Aydar Kamaltdinov <[email protected]> -------------------- Commit message for microsoft/vscode-python@8496dfe: Remove experimental flag for create env prompt (microsoft/vscode-python#22892) Remove experimental flag for `python.createEnvironment.trigger`. -------------------- Commit message for microsoft/vscode-python@c4c05a6: update tree comparison for tests to be order independent for children (microsoft/vscode-python#22832) following the introduction of pytest 8, the order in which children were listed changed. Since the order is not important, this updates the tests to make the tests not consider order of children when comparing actual and expected outcomes of test runs. -------------------- Commit message for microsoft/vscode-python@4030717: Use terminal data write event to figure out whether shell integration is working (microsoft/vscode-python#22872) Closes microsoft/vscode-python#22439 Blocked on microsoft/vscode#204616 -------------------- Commit message for microsoft/vscode-python@d674a17: Fix Run Recent Command Caching Issue (microsoft/vscode-python#22867) Resolves: microsoft/vscode-python#22811 Fixing caching issue where users were experiencing cached success/failure decoration that were impacted when using `Terminal: Run Recent Command` on success/failure commands -------------------- Commit message for microsoft/vscode-python@c0bf1b7: Improve time taken to trigger language server startup once extension activation is triggered (microsoft/vscode-python#22514) For microsoft/vscode-python#22146 Improves time taken to trigger language server startup once extension activation is triggered - Do not block discovery on windows registry - Do not blocking auto-selection on validation of all interpreters - Make Windows Path locator faster -------------------- Commit message for microsoft/vscode-python@20c1a10: Log when running Python file (microsoft/vscode-python#22851) For microsoft/vscode-python#22711 -------------------- Commit message for microsoft/vscode-python@8aaa70e: Fix venv activation for cshell (microsoft/vscode-python#22852) Closes microsoft/vscode-python#22822 Use current shell to figure out whether shell integration is working, even when using fallback shell for getting environment variables. -------------------- Commit message for microsoft/vscode-python@1626c46: Do not run commands to check whether shell integration is working (microsoft/vscode-python#22850) Closes microsoft/vscode-python#22774 closes microsoft/vscode-python#22743 -------------------- Commit message for microsoft/vscode-python@13a6727: include multiple pytest versions in PR check (microsoft/vscode-python#22813) update PR check workflow to include testing Python tests against 3 versions of pytest: pre-release, stable release, and oldest supported version. --------- Co-authored-by: Karthik Nadig <[email protected]> -------------------- Commit message for microsoft/vscode-python@6e8c56c: Bump dev version 2024.1 (microsoft/vscode-python#22805) Lead-authored-by: Kartik Raj <[email protected]> Co-authored-by: Aydar Kamaltdinov <[email protected]> Co-authored-by: paulacamargo25 <[email protected]> Co-authored-by: Luciana Abud <[email protected]> Co-authored-by: Courtney Webster <[email protected]> Co-authored-by: Anthony Kim <[email protected]> Co-authored-by: Isabel Zimmerman <[email protected]> Co-authored-by: Eleanor Boyd <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: GitHub <[email protected]>
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Mar 28, 2024
…from upstream Merge pull request #277 from posit-dev/merge/2023.22 Merge vscode-python 2023.22 from upstream -------------------- Commit message for posit-dev/positron-python@2e3ea32: handle new upstream `deprecated` response upon parser error -------------------- Commit message for posit-dev/positron-python@d50c326: Update yarn.lock -------------------- Commit message for posit-dev/positron-python@105bf9d: Merge commit 'a0cddbdf0939729cdb82dca2d129433ad475f51e' -------------------- Commit message for microsoft/vscode-python@a0cddbd: bump-release-2023.22 (microsoft/vscode-python#22587) bump to release version 2023.22 and update package.json -------------------- Commit message for microsoft/vscode-python@5302d0e: Revert unsuccessful REPL decoration fix and disable for windows (microsoft/vscode-python#22578) Reverting microsoft/vscode-python#22572 since it is producing color decoration on weird Python REPL spot for Windows pwsh users, and disable decoration entirely for Windows pwsh users temporarily while trying to fix specific problem. Disable feature for stable. Refer: microsoft/vscode-python#22546 microsoft/vscode-python#22535 -------------------- Commit message for microsoft/vscode-python@bffc9b3: Fix shell integration decoration bug for Windows pwsh (microsoft/vscode-python#22572) Attempt to fix colorless and randomized circle decoration for Python REPL usage by Windows Powershell users. Resolves: microsoft/vscode-python#22546 microsoft/vscode-python#22535 -------------------- Commit message for microsoft/vscode-python@e1b54d0: fix no test id provided for pytest run (microsoft/vscode-python#22569) fixes microsoft/vscode-python#22567 Now if a user tries to click the "run" button a empty folder (ie a folder with no tests in it) it will just run pytest with no testIds as args and notify the user. -------------------- Commit message for microsoft/vscode-python@61fcf3a: Properly build deactivate commands for powershell (microsoft/vscode-python#22570) For microsoft/vscode-python#20950 -------------------- Commit message for microsoft/vscode-python@db6e15e: Do not throw if initializing deactivate script fails (microsoft/vscode-python#22566) For microsoft/vscode-python#20950 -------------------- Commit message for microsoft/vscode-python@caa50dc: Fix shell integration decoration for windows pwsh (microsoft/vscode-python#22560) Attempting to fix shell integration decoration glitch for windows pwsh when using Python REPL from VS Code. Resolves: microsoft/vscode-python#22546 microsoft/vscode-python#22535 -------------------- Commit message for microsoft/vscode-python@3efb54f: White space after REPL prompt (microsoft/vscode-python#22549) There should be white space after new REPL prompt that I override for purpose of shell integration. Resolves: microsoft/vscode-python#22548 -------------------- Commit message for microsoft/vscode-python@261ae66: Improvement: Pass along python interpreter to jedi-language-server (microsoft/vscode-python#22466) Fixes microsoft/vscode-python#22495 ## Before this PR Overriding the Python interpreter to a different environment that isn't the current globally-activated base environment would yield no completions when Jedi is used as the underlying language server. Example [stackoverflow question](https://stackoverflow.com/questions/62018436/vscode-intellisense-code-completion-doesnt-work-when-i-am-not-in-base-conda-e) hitting the same issue. ## After this PR We now pass along the interpreter path to jedi-language-server as part of the initial options under `workspace.environmentPath` ([ref](https://github.com/pappasam/jedi-language-server/#workspaceenvironmentpath)) -------------------- Commit message for microsoft/vscode-python@1639753: switch to conditional error message on check for UUID and port during pytest config (microsoft/vscode-python#22534) fixes microsoft/vscode-python#19857 -------------------- Commit message for microsoft/vscode-python@9a5363c: Resolve test suite discovery import errors due to path ordering (microsoft/vscode-python#22454) [Issue microsoft/vscode-python#22453](microsoft/vscode-python#22453) - Once starting to run discovery, add the projects root path to PATH at index 0 so that any further imports will use the projects root directory and not reference the incorrect directory. - Since the test suite only allows the start_dir to be one directory deep, we can conclude that if the start_dir is not "." or contains a "/", that we need to add that start_dir's parent to PATH. Otherwise, we simply add the start_dir to PATH. -------------------- Commit message for microsoft/vscode-python@eb96141: Use shell integration to denote success/failure (microsoft/vscode-python#22487) Resolves: microsoft/vscode-python#22486 Use shell integration to denote success/failure in Python REPL launched from VS Code. This would mean having the blue or red decorators based on whether or not user's command succeeded. -------------------- Commit message for microsoft/vscode-python@f6e1338: Use worker threads for fetching conda environments and interpreter related info (microsoft/vscode-python#22481) -------------------- Commit message for microsoft/vscode-python@3c552f9: Show warning and allow user to turn off smart send for deprecated Python code (microsoft/vscode-python#22353) Resolves: microsoft/vscode-python#22341 microsoft/vscode-python#22340 Showing warning message after detecting user is on Python file with deprecated Python code, and are attempting to run smart send via shift+enter action. Allow user to turn off this via workspace setting. --------- Co-authored-by: Courtney Webster <[email protected]> Co-authored-by: Kartik Raj <[email protected]> -------------------- Commit message for microsoft/vscode-python@ef983f4: Bump `vscode-tas-client` and fix tests (microsoft/vscode-python#22493) Closes microsoft/vscode-python#22461 Sinon requires the actual object definition, so we need to point it to the module file that actually has the function. -------------------- Commit message for microsoft/vscode-python@9298b2c: Bump dessant/lock-threads from 4 to 5 (microsoft/vscode-python#22474) Bumps [dessant/lock-threads](https://github.com/dessant/lock-threads) from 4 to 5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dessant/lock-threads/releases">dessant/lock-threads's releases</a>.</em></p> <blockquote> <h2>v5.0.0</h2> <p>Learn more about this release from the <a href="https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md#changelog">changelog</a>.</p> <h2>v4.0.1</h2> <p>Learn more about this release from the <a href="https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md#changelog">changelog</a>.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md">dessant/lock-threads's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/dessant/lock-threads/compare/v4.0.1...v5.0.0">5.0.0</a> (2023-11-14)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>Discussions are also processed by default, set the <code>process-only</code> input parameter to preserve the old behavior</li> </ul> <pre lang="yaml"><code> steps: - uses: dessant/lock-threads@v5 with: process-only: 'issues, prs' </code></pre> <ul> <li>the action now requires Node.js 20</li> </ul> <h3>Features</h3> <ul> <li>lock discussions (<a href="https://github.com/dessant/lock-threads/commit/0a0976f3ded51c88c6128dd96dd115c9f14fa764">0a0976f</a>), closes <a href="https://redirect.github.com/dessant/lock-threads/issues/25">#25</a></li> </ul> <h3>Bug Fixes</h3> <ul> <li>update dependencies (<a href="https://github.com/dessant/lock-threads/commit/5a25b54eae3e7a5580d09ef0f7cbc5b18376db67">5a25b54</a>)</li> </ul> <h3><a href="https://github.com/dessant/lock-threads/compare/v4.0.0...v4.0.1">4.0.1</a> (2023-06-12)</h3> <h3>Bug Fixes</h3> <ul> <li>retry and throttle GitHub API requests (<a href="https://github.com/dessant/lock-threads/commit/1618e91da69b9fe614fb9837ac673ea4600eb529">1618e91</a>), closes <a href="https://redirect.github.com/dessant/lock-threads/issues/35">#35</a></li> </ul> <h2><a href="https://github.com/dessant/lock-threads/compare/v3.0.0...v4.0.0">4.0.0</a> (2022-12-04)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>the action now requires Node.js 16</li> </ul> <h3>Bug Fixes</h3> <ul> <li>update dependencies (<a href="https://github.com/dessant/lock-threads/commit/38e918558115222435d26c0639870cdbe3572929">38e9185</a>)</li> <li>update docs (<a href="https://github.com/dessant/lock-threads/commit/32986e26965060a85db09e98ef7e5958c961ae84">32986e2</a>)</li> </ul> <h2><a href="https://github.com/dessant/lock-threads/compare/v2.1.2...v3.0.0">3.0.0</a> (2021-09-27)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>input parameter names have changed</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dessant/lock-threads/commit/d42e5f49803f3c4e14ffee0378e31481265dda22"><code>d42e5f4</code></a> chore(release): 5.0.0</li> <li><a href="https://github.com/dessant/lock-threads/commit/d8da6c1485cbe748b5b632f1a52cf2a52941cbf9"><code>d8da6c1</code></a> chore: update package</li> <li><a href="https://github.com/dessant/lock-threads/commit/c1eab4b45f97073a922fbd226afab0e34a70cf5f"><code>c1eab4b</code></a> chore: update workflow</li> <li><a href="https://github.com/dessant/lock-threads/commit/0a0976f3ded51c88c6128dd96dd115c9f14fa764"><code>0a0976f</code></a> feat: lock discussions</li> <li><a href="https://github.com/dessant/lock-threads/commit/53f3f0c0b9158bece84746885adc5f4bf2dd1ddc"><code>53f3f0c</code></a> chore: migrate package to ESM</li> <li><a href="https://github.com/dessant/lock-threads/commit/5a25b54eae3e7a5580d09ef0f7cbc5b18376db67"><code>5a25b54</code></a> fix: update dependencies</li> <li>See full diff in <a href="https://github.com/dessant/lock-threads/compare/v4...v5">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for microsoft/vscode-python@e27185a: Use worker threads for fetching Windows Registry interpreters (microsoft/vscode-python#22479) For microsoft/vscode-python#22146 -------------------- Commit message for microsoft/vscode-python@7a4de92: Use `WorkspaceFolder.name` in addition to workspace folder's basename when resolving `${workspaceFolder:name}` syntax in settings (microsoft/vscode-python#22471) Closes microsoft/vscode-python#22452 -------------------- Commit message for microsoft/vscode-python@fbfa126: Add 3.12 to conda version list (microsoft/vscode-python#22470) -------------------- Commit message for microsoft/vscode-python@47552a3: Install requirements before toml (microsoft/vscode-python#22468) Fixes microsoft/vscode-python#22423 -------------------- Commit message for microsoft/vscode-python@a1fac81: If active editor opened is outside the editor, activate the first workspace (microsoft/vscode-python#22450) For microsoft/vscode-python#22449 -------------------- Commit message for microsoft/vscode-python@b68ddee: Support deactivating virtual environments without user intervention (microsoft/vscode-python#22405) Closes microsoft/vscode-python#22448 Adds deactivate script to `PATH` -------------------- Commit message for microsoft/vscode-python@8d174a8: Fix shell integration API reliability (microsoft/vscode-python#22446) microsoft/vscode-python#22440 It leads to terminals activating forever. -------------------- Commit message for microsoft/vscode-python@1b3c1ea: Adding `Locked` comments to walkthrough commands (microsoft/vscode-python#22432) Adds comments to lock command names for walkthrough localization. Only added Locked comments for walkthrough tiles that are in use and have commands -------------------- Commit message for microsoft/vscode-python@2fc9fea: Revert "Reliably detect whether shell integration is working" (microsoft/vscode-python#22445) Reverts microsoft/vscode-python#22440 It seems reactivating never finishes after this, although this doesn't repro when debugging the extension, have to investigate further. -------------------- Commit message for microsoft/vscode-python@f98caf6: Add consoleTitle to launch.json properties schema (microsoft/vscode-python#22406) consoleTitle is effectively an undocumented feature. pydebug accepts the config key, but vscode will report a problem because it is missing from the schema. see [this debugpy issue](microsoft/debugpy#1178) and [#13040](microsoft/vscode-python#13040) I used the phrase "console or terminal" because I noticed the name was represented on both integratedTerminal and internalConsole. I didn't test externalTerminal. --------- Co-authored-by: Luciana Abud <[email protected]> -------------------- Commit message for microsoft/vscode-python@2a976e3: Reliably detect whether shell integration is working (microsoft/vscode-python#22440) Closes microsoft/vscode-python#22439 Blocked on https://github.com/microsoft/vscode-distro/pull/822 -------------------- Commit message for microsoft/vscode-python@67b4801: Improve shell identifier on case-insensitive system (microsoft/vscode-python#22391) Use case-insensitive regex to remove `.exe` extension. See: microsoft/vscode-python#22036 (comment) -------------------- Commit message for microsoft/vscode-python@7bc45e5: Do not attempt to kill the process if it has already exited (microsoft/vscode-python#22424) Closes microsoft/vscode-python#22420 This bugs seems to have existed every since `rawProcessApi.ts` was created. `proc.killed` can be `false` even after process has exited. -------------------- Commit message for microsoft/vscode-python@f6cfa6e: Remove old code for folder support in interpreter path setting (microsoft/vscode-python#22413) Closes microsoft/vscode-python#12452 Lead-authored-by: Kartik Raj <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Courtney Webster <[email protected]> Co-authored-by: John H. Ayad <[email protected]> Co-authored-by: Wasim Lorgat <[email protected]> Co-authored-by: Shane Saravia <[email protected]> Co-authored-by: Trysten <[email protected]> Co-authored-by: JamzumSum <[email protected]> Co-authored-by: Eleanor Boyd <[email protected]> Co-authored-by: Karthik Nadig <[email protected]> Co-authored-by: Pete Farland <[email protected]> Co-authored-by: Anthony Kim <[email protected]> Signed-off-by: GitHub <[email protected]>
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Mar 28, 2024
Merge pull request #395 from posit-dev/merge/v2024.2.0 Merge upstream: `v2024.2.0` -------------------- Commit message for posit-dev/positron-python@7d85a51: ignore pyright errors in ms testing files -------------------- Commit message for posit-dev/positron-python@f9a3259: Bump flask from 3.0.1 to 3.0.2 (posit-dev/positron-python#354) Bumps [flask](https://github.com/pallets/flask) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/pallets/flask/releases) - [Changelog](https://github.com/pallets/flask/blob/main/CHANGES.rst) - [Commits](pallets/flask@3.0.1...3.0.2) --- updated-dependencies: - dependency-name: flask dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@ea812a4: Bump ipywidgets from 8.1.1 to 8.1.2 (posit-dev/positron-python#368) Bumps [ipywidgets](https://github.com/jupyter-widgets/ipywidgets) from 8.1.1 to 8.1.2. - [Release notes](https://github.com/jupyter-widgets/ipywidgets/releases) - [Commits](jupyter-widgets/ipywidgets@8.1.1...8.1.2) --- updated-dependencies: - dependency-name: ipywidgets dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Isabel Zimmerman <[email protected]> -------------------- Commit message for posit-dev/positron-python@e3a5399: Bump pyright from 1.1.349 to 1.1.351 (posit-dev/positron-python#379) Bumps [pyright](https://github.com/RobertCraigie/pyright-python) from 1.1.349 to 1.1.351. - [Release notes](https://github.com/RobertCraigie/pyright-python/releases) - [Commits](RobertCraigie/pyright-python@v1.1.349...v1.1.351) --- updated-dependencies: - dependency-name: pyright dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@2eeb677: Bump polars from 0.20.6 to 0.20.11 (posit-dev/positron-python#394) Bumps [polars](https://github.com/pola-rs/polars) from 0.20.6 to 0.20.11. - [Release notes](https://github.com/pola-rs/polars/releases) - [Commits](pola-rs/polars@py-0.20.6...py-0.20.11) --- updated-dependencies: - dependency-name: polars dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@573d9fd: Bump ipykernel from 6.29.0 to 6.29.3 (posit-dev/positron-python#390) Bumps [ipykernel](https://github.com/ipython/ipykernel) from 6.29.0 to 6.29.3. - [Release notes](https://github.com/ipython/ipykernel/releases) - [Changelog](https://github.com/ipython/ipykernel/blob/main/CHANGELOG.md) - [Commits](ipython/ipykernel@v6.29.0...v6.29.3) --- updated-dependencies: - dependency-name: ipykernel dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for posit-dev/positron-python@334b383: update package.json -------------------- Commit message for posit-dev/positron-python@7ce08b1: Merge tag 'v2024.2.0' into merge/v2024.2.0 -------------------- Commit message for posit-dev/positron-python@063ba15: Finalized-release-2024.2.0 (posit-dev/positron-python#22996) Finalized release 2024.2.0: removing -rc -------------------- Commit message for posit-dev/positron-python@3eef025: Bump release 2024.2 (posit-dev/positron-python#22972) Bump release 2024.2 -------------------- Commit message for posit-dev/positron-python@1fbd77b: skip tests, pytest upstream regression (posit-dev/positron-python#22974) Short-term fix to stop CI from failing due to a regression upstream from pytest. See issue for details: microsoft/vscode-python#22965. -------------------- Commit message for microsoft/vscode-python@4fca030: Adding GDPR tag for isFirstSession (microsoft/vscode-python#22955) -------------------- Commit message for microsoft/vscode-python@ba94553: Modify telemetry to contain trigger time as property (microsoft/vscode-python#22941) -------------------- Commit message for microsoft/vscode-python@178a0b2: Fix bug with symlink for pytest execution (microsoft/vscode-python#22952) Fixes microsoft/vscode-python#22938 -------------------- Commit message for microsoft/vscode-python@bae7d40: Update vscode-tas-client version (microsoft/vscode-python#22876) -------------------- Commit message for microsoft/vscode-python@75ed73e: Fix Bug with Pytest when using symlinked workspaces (microsoft/vscode-python#22885) fixes microsoft/vscode-python#22658 also implements switching to arg mapping which is this issue here: microsoft/vscode-python#22076 --------- Co-authored-by: Karthik Nadig <[email protected]> -------------------- Commit message for microsoft/vscode-python@e53651d: Prevent first Python command being lost (microsoft/vscode-python#22902) Fixes: microsoft/vscode-python#22673 Fixes: microsoft/vscode-python#22545 Fixes: microsoft/vscode-python#22691 Making best effort to address issue where very first command sent to REPL via Terminal gets ignored, or gets pasted both in Terminal and in REPL. With the fix, we observe whether Python REPL is launched in Terminal via VS Code's `onDidWriteTerminalData` and send the command, or wait three seconds as a fallback mechanism. These two combined together will significantly reduce or resolve all-together the chance of very first command being swollen up or gets pasted twice in Terminal and REPL previously where it did not have context of whether Python REPL instance have started inside the Terminal or not. -------------------- Commit message for microsoft/vscode-python@a60fbd5: Add GDPR tags for new Pylance properties (microsoft/vscode-python#22922) -------------------- Commit message for microsoft/vscode-python@aff0b05: Use python debugger in testing (microsoft/vscode-python#22903) closed: microsoft/vscode-python-debugger#174 -------------------- Commit message for microsoft/vscode-python@84734a8: Updating installed extensions section of README.md (microsoft/vscode-python#22893) Adding the Python Debugger to the installed extensions section of the README. -------------------- Commit message for microsoft/vscode-python@2159238: Bump actions/setup-python from 4 to 5 in /.github/actions/build-vsix (microsoft/vscode-python#22602) Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/setup-python/releases">actions/setup-python's releases</a>.</em></p> <blockquote> <h2>v5.0.0</h2> <h2>What's Changed</h2> <p>In scope of this release, we update node version runtime from node16 to node20 (<a href="https://redirect.github.com/actions/setup-python/pull/772">actions/setup-python#772</a>). Besides, we update dependencies to the latest versions.</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-python/compare/v4.8.0...v5.0.0">https://github.com/actions/setup-python/compare/v4.8.0...v5.0.0</a></p> <h2>v4.8.0</h2> <h2>What's Changed</h2> <p>In scope of this release we added support for GraalPy (<a href="https://redirect.github.com/actions/setup-python/pull/694">actions/setup-python#694</a>). You can use this snippet to set up GraalPy:</p> <pre lang="yaml"><code>steps: - uses: actions/checkout@v4 - uses: actions/setup-python@v4 with: python-version: 'graalpy-22.3' - run: python my_script.py </code></pre> <p>Besides, the release contains such changes as:</p> <ul> <li>Trim python version when reading from file by <a href="https://github.com/FerranPares"><code>@FerranPares</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/628">actions/setup-python#628</a></li> <li>Use non-deprecated versions in examples by <a href="https://github.com/jeffwidman"><code>@jeffwidman</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/724">actions/setup-python#724</a></li> <li>Change deprecation comment to past tense by <a href="https://github.com/jeffwidman"><code>@jeffwidman</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/723">actions/setup-python#723</a></li> <li>Bump <code>@babel/traverse</code> from 7.9.0 to 7.23.2 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/743">actions/setup-python#743</a></li> <li>advanced-usage.md: Encourage the use actions/checkout@v4 by <a href="https://github.com/cclauss"><code>@cclauss</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/729">actions/setup-python#729</a></li> <li>Examples now use checkout@v4 by <a href="https://github.com/simonw"><code>@simonw</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/738">actions/setup-python#738</a></li> <li>Update actions/checkout to v4 by <a href="https://github.com/dmitry-shibanov"><code>@dmitry-shibanov</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/761">actions/setup-python#761</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/FerranPares"><code>@FerranPares</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-python/pull/628">actions/setup-python#628</a></li> <li><a href="https://github.com/timfel"><code>@timfel</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-python/pull/694">actions/setup-python#694</a></li> <li><a href="https://github.com/jeffwidman"><code>@jeffwidman</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-python/pull/724">actions/setup-python#724</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-python/compare/v4...v4.8.0">https://github.com/actions/setup-python/compare/v4...v4.8.0</a></p> <h2>v4.7.1</h2> <h2>What's Changed</h2> <ul> <li>Bump word-wrap from 1.2.3 to 1.2.4 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/702">actions/setup-python#702</a></li> <li>Add range validation for toml files by <a href="https://github.com/dmitry-shibanov"><code>@dmitry-shibanov</code></a> in <a href="https://redirect.github.com/actions/setup-python/pull/726">actions/setup-python#726</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-python/compare/v4...v4.7.1">https://github.com/actions/setup-python/compare/v4...v4.7.1</a></p> <h2>v4.7.0</h2> <p>In scope of this release, the support for reading python version from pyproject.toml was added (<a href="https://redirect.github.com/actions/setup-python/pull/669">actions/setup-python#669</a>).</p> <pre lang="yaml"><code> - name: Setup Python uses: actions/setup-python@v4 </tr></table> </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/setup-python/commit/0a5c61591373683505ea898e09a3ea4f39ef2b9c"><code>0a5c615</code></a> Update action to node20 (<a href="https://redirect.github.com/actions/setup-python/issues/772">#772</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/0ae58361cdfd39e2950bed97a1e26aa20c3d8955"><code>0ae5836</code></a> Add example of GraalPy to docs (<a href="https://redirect.github.com/actions/setup-python/issues/773">#773</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/b64ffcaf5b410884ad320a9cfac8866006a109aa"><code>b64ffca</code></a> update actions/checkout to v4 (<a href="https://redirect.github.com/actions/setup-python/issues/761">#761</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/8d2896179abf658742de432b3f203d2c2d86a587"><code>8d28961</code></a> Examples now use checkout@v4 (<a href="https://redirect.github.com/actions/setup-python/issues/738">#738</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/7bc6abb01e0555719edc2dbca70a2fde309e5e56"><code>7bc6abb</code></a> advanced-usage.md: Encourage the use actions/checkout@v4 (<a href="https://redirect.github.com/actions/setup-python/issues/729">#729</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/e8111cec9d3dc15220d8a3b638f08419f57b906a"><code>e8111ce</code></a> Bump <code>@babel/traverse</code> from 7.9.0 to 7.23.2 (<a href="https://redirect.github.com/actions/setup-python/issues/743">#743</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/a00ea43da65e7c04d2bdae58b3afecd77057eb9e"><code>a00ea43</code></a> add fix for graalpy ci (<a href="https://redirect.github.com/actions/setup-python/issues/741">#741</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/8635b1ccc5934e73ed3510980fd2e7790b85839b"><code>8635b1c</code></a> Change deprecation comment to past tense (<a href="https://redirect.github.com/actions/setup-python/issues/723">#723</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/f6cc428f535856f9c23558d01765a42a4d6cf758"><code>f6cc428</code></a> Use non-deprecated versions in examples (<a href="https://redirect.github.com/actions/setup-python/issues/724">#724</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/5f2af211d616f86005883b44826180b21abb4060"><code>5f2af21</code></a> Add GraalPy support (<a href="https://redirect.github.com/actions/setup-python/issues/694">#694</a>)</li> <li>Additional commits viewable in <a href="https://github.com/actions/setup-python/compare/v4...v5">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> -------------------- Commit message for microsoft/vscode-python@83cf53b: Add "isMeasurement" for LANGUAGE_SERVER_TRIGGER_DURATION (microsoft/vscode-python#22912) cc/ @cwebster-99 -------------------- Commit message for microsoft/vscode-python@7be33eb: Add more shell integration sequences to check for (microsoft/vscode-python#22911) Based on discussion with Daniel For microsoft/vscode-python#22440 -------------------- Commit message for microsoft/vscode-python@6838ccf: Do not activate microvenv if terminal.activateEnvironment is set to false and when not in terminal experiment (microsoft/vscode-python#22909) -------------------- Commit message for microsoft/vscode-python@2dc158e: Log options being passed when using environment collection APIs (microsoft/vscode-python#22907) For microsoft/vscode-python#22899 -------------------- Commit message for microsoft/vscode-python@5f971ae: Prepend `PATH` both at shell integration and process creation (microsoft/vscode-python#22905) -------------------- Commit message for microsoft/vscode-python@5174d5c: Improve shell integration reliability for zsh (microsoft/vscode-python#22891) Closes microsoft/vscode-python#22881 If status changes, re-run activation. Also persist once we know shell integration works for a shell. -------------------- Commit message for microsoft/vscode-python@b0c34e3: Add UnicodeDecodeError catching (microsoft/vscode-python#22873) Resolve `UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd0 in position 48995: unexpected end of data` Co-authored-by: Aydar Kamaltdinov <[email protected]> -------------------- Commit message for microsoft/vscode-python@8496dfe: Remove experimental flag for create env prompt (microsoft/vscode-python#22892) Remove experimental flag for `python.createEnvironment.trigger`. -------------------- Commit message for microsoft/vscode-python@c4c05a6: update tree comparison for tests to be order independent for children (microsoft/vscode-python#22832) following the introduction of pytest 8, the order in which children were listed changed. Since the order is not important, this updates the tests to make the tests not consider order of children when comparing actual and expected outcomes of test runs. -------------------- Commit message for microsoft/vscode-python@4030717: Use terminal data write event to figure out whether shell integration is working (microsoft/vscode-python#22872) Closes microsoft/vscode-python#22439 Blocked on microsoft/vscode#204616 -------------------- Commit message for microsoft/vscode-python@d674a17: Fix Run Recent Command Caching Issue (microsoft/vscode-python#22867) Resolves: microsoft/vscode-python#22811 Fixing caching issue where users were experiencing cached success/failure decoration that were impacted when using `Terminal: Run Recent Command` on success/failure commands -------------------- Commit message for microsoft/vscode-python@c0bf1b7: Improve time taken to trigger language server startup once extension activation is triggered (microsoft/vscode-python#22514) For microsoft/vscode-python#22146 Improves time taken to trigger language server startup once extension activation is triggered - Do not block discovery on windows registry - Do not blocking auto-selection on validation of all interpreters - Make Windows Path locator faster -------------------- Commit message for microsoft/vscode-python@20c1a10: Log when running Python file (microsoft/vscode-python#22851) For microsoft/vscode-python#22711 -------------------- Commit message for microsoft/vscode-python@8aaa70e: Fix venv activation for cshell (microsoft/vscode-python#22852) Closes microsoft/vscode-python#22822 Use current shell to figure out whether shell integration is working, even when using fallback shell for getting environment variables. -------------------- Commit message for microsoft/vscode-python@1626c46: Do not run commands to check whether shell integration is working (microsoft/vscode-python#22850) Closes microsoft/vscode-python#22774 closes microsoft/vscode-python#22743 -------------------- Commit message for microsoft/vscode-python@13a6727: include multiple pytest versions in PR check (microsoft/vscode-python#22813) update PR check workflow to include testing Python tests against 3 versions of pytest: pre-release, stable release, and oldest supported version. --------- Co-authored-by: Karthik Nadig <[email protected]> -------------------- Commit message for microsoft/vscode-python@6e8c56c: Bump dev version 2024.1 (microsoft/vscode-python#22805) Lead-authored-by: Kartik Raj <[email protected]> Co-authored-by: Aydar Kamaltdinov <[email protected]> Co-authored-by: paulacamargo25 <[email protected]> Co-authored-by: Luciana Abud <[email protected]> Co-authored-by: Courtney Webster <[email protected]> Co-authored-by: Anthony Kim <[email protected]> Co-authored-by: Isabel Zimmerman <[email protected]> Co-authored-by: Eleanor Boyd <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: GitHub <[email protected]>
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Apr 5, 2024
…hon#22964) Failing tests are due to microsoft/vscode-python#22965, this can still be reviewed. Closes microsoft/vscode-python#22918 closes microsoft/vscode-python#22146
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Apr 5, 2024
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Apr 8, 2024
…hon#22964) Failing tests are due to microsoft/vscode-python#22965, this can still be reviewed. Closes microsoft/vscode-python#22918 closes microsoft/vscode-python#22146
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Apr 8, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
#21755
Spike results
Based on CPU profiles in #21755 (comment) discovery is mainly blocked by:
Note spawning python binaries is fine, it blocks very little of the time.
The text was updated successfully, but these errors were encountered: