Skip to content

Revert commits changing Ctrl-C behavior on 1.13#61065

Merged
KristofferC merged 5 commits intobackports-release-1.13from
kc/ctrl_c_revert
Mar 18, 2026
Merged

Revert commits changing Ctrl-C behavior on 1.13#61065
KristofferC merged 5 commits intobackports-release-1.13from
kc/ctrl_c_revert

Conversation

@KristofferC
Copy link
Copy Markdown
Member

Trying to fix #58689 on 1.13 by reverting relevant commits.

@KristofferC KristofferC added the revert This reverts a previously merged PR. label Feb 18, 2026
@KristofferC KristofferC changed the title Revert commits changing Ctrl-C behavoir on 1.13 Revert commits changing Ctrl-C behavior on 1.13 Feb 18, 2026
Copy link
Copy Markdown
Member

@topolarity topolarity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems the way to go to me, until we get proper cancellation.

@vtjnash let us know if #59669 is worth back-porting / re-working for 1.13

@cstjean
Copy link
Copy Markdown
Contributor

cstjean commented Mar 10, 2026

Curious, but will this be an improvement over 1.12? On my Windows machine with MTK, Ctrl-C segfaults about 90% of the time.

Base automatically changed from backports-release-1.13 to release-1.13 March 13, 2026 16:12
@KristofferC KristofferC changed the base branch from release-1.13 to backports-release-1.13 March 18, 2026 13:33
@KristofferC KristofferC merged commit 8fa5c01 into backports-release-1.13 Mar 18, 2026
8 checks passed
@KristofferC KristofferC deleted the kc/ctrl_c_revert branch March 18, 2026 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

revert This reverts a previously merged PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants