dotnet SIGTERM signal handler registration #50983
Merged
+49
−17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR is targeting |
Youssef1313
reviewed
Sep 24, 2025
baronfel
approved these changes
Sep 24, 2025
c126b90 to
629e887
Compare
This was referenced Sep 24, 2025
3 tasks
Youssef1313
reviewed
Sep 26, 2025
|
Known GenerateBundle task failure |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes regression caused by a breaking change as recommended in dotnet/docs#46226.
Fixes #50965
Customer Impact
Impacts customers using dotnet-watch on Unix. dotnet-watch is unable to gracefully terminate the target process.
Regression?
Regressed from .NET 9 due to dotnet/docs#46226
Risk
Justification: The change registers POSIX signal handler since the runtime does not register it by default anymore.
Verification
Packaging changes reviewed?