Skip to content

Conversation

karthiknadig
Copy link
Member

@karthiknadig karthiknadig commented Feb 8, 2022

Closes #18455

@karthiknadig karthiknadig requested a review from karrtikr February 8, 2022 19:22
@karthiknadig karthiknadig added no-changelog No news entry required skip tests Updates to tests unnecessary and removed no-changelog No news entry required labels Feb 8, 2022
@karthiknadig karthiknadig merged commit 41de489 into microsoft:main Feb 8, 2022
@karthiknadig karthiknadig deleted the fix-isort branch February 8, 2022 20:07
karthiknadig added a commit to karthiknadig/vscode-python that referenced this pull request Feb 8, 2022
* Fix `invalid patch string` error when using conda

* Fix tests
karthiknadig added a commit that referenced this pull request Feb 8, 2022
* Update release version and change log for point release

* update changelog

* Fix `invalid patch string` error when using conda (#18481)

* Fix `invalid patch string` error when using conda

* Fix tests

* Update change log
@karrtikr
Copy link

karrtikr commented Feb 9, 2022

@karthiknadig
Copy link
Member Author

Seems like it was some flaky ness, no errors in the main build: https://github.com/microsoft/vscode-python/actions/runs/1814445017

karthiknadig added a commit that referenced this pull request Feb 10, 2022
* Fix conda run output marker script (#18412) (#18413)

* Fix marker script support for '-c' flag (#18418)

* Fix the interpreter selected by 'new venv' prompt (#18417)

* Update version and changelog for release (#18421)

* Use older way of launching debugger when using conda less than 4.9.0 (#18451)

* CI failures: Pin prospector to 1.6.0, pytest to < 7.0.0, and fix linting issues with flake8 3.9.2 (#18446)

* See if pinning pip works

* Pin in pr check

* Pin pip everywhere else

* angery

* Undo pip changes

* Pin pytest < 7.0.0

* Fix linting?

* Update release version and change log for point release (#18470)

* Update release version and change log for point release

* update changelog

* Fix `invalid patch string` error when using conda (#18481)

* Fix `invalid patch string` error when using conda

* Fix tests

* Update change log

* Cleanup news files

Co-authored-by: Kartik Raj <karraj@microsoft.com>
Co-authored-by: Kim-Adeline Miguel <51720070+kimadeline@users.noreply.github.com>
wesm pushed a commit to posit-dev/positron that referenced this pull request Mar 28, 2024
…ython#18481)

* Fix `invalid patch string` error when using conda

* Fix tests
wesm pushed a commit to posit-dev/positron that referenced this pull request Mar 28, 2024
* Fix conda run output marker script (microsoft/vscode-python#18412) (microsoft/vscode-python#18413)

* Fix marker script support for '-c' flag (microsoft/vscode-python#18418)

* Fix the interpreter selected by 'new venv' prompt (microsoft/vscode-python#18417)

* Update version and changelog for release (microsoft/vscode-python#18421)

* Use older way of launching debugger when using conda less than 4.9.0 (microsoft/vscode-python#18451)

* CI failures: Pin prospector to 1.6.0, pytest to < 7.0.0, and fix linting issues with flake8 3.9.2 (microsoft/vscode-python#18446)

* See if pinning pip works

* Pin in pr check

* Pin pip everywhere else

* angery

* Undo pip changes

* Pin pytest < 7.0.0

* Fix linting?

* Update release version and change log for point release (microsoft/vscode-python#18470)

* Update release version and change log for point release

* update changelog

* Fix `invalid patch string` error when using conda (microsoft/vscode-python#18481)

* Fix `invalid patch string` error when using conda

* Fix tests

* Update change log

* Cleanup news files

Co-authored-by: Kartik Raj <karraj@microsoft.com>
Co-authored-by: Kim-Adeline Miguel <51720070+kimadeline@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip tests Updates to tests unnecessary

Projects

None yet

Development

Successfully merging this pull request may close these issues.

'Invalid patch string:'

2 participants