-
Notifications
You must be signed in to change notification settings - Fork 10.6k
React to SIGTERM exit code change #6526
Copy link
Copy link
Closed
Labels
DoneThis issue has been fixedThis issue has been fixedarea-hostingIncludes HostingIncludes Hostingarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.
Milestone
Metadata
Metadata
Assignees
Labels
DoneThis issue has been fixedThis issue has been fixedarea-hostingIncludes HostingIncludes Hostingarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.
Type
Fields
Give feedbackNo fields configured for issues without a type.
dotnet/coreclr#21300 (comment)
CoreClr is changing the default behavior for SIGTERM exit codes from zero to non-zero. WebHost and GenericHost both block the ProcessExit event while attempting to shut down.
Proposal:
If the host does shut down gracefully then set the exit code to zero.