Closed paulyuk closed 12 months ago
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
Expected Behavior
Stopping, CTL-C, fg, SIGTERM, SIGKILL on dapr.exe never leave the app runtime process running
Actual Behavior
It's all to easy to do an action, stop and the runtime process is still running (taking up memory, and blocking your port!)
Steps to Reproduce the Problem
Our own examples repro the problem and require LSOF->Kill -9 scripts:
https://github.com/dapr/go-sdk/blob/main/examples/actor/README.md?plain=1#L79 https://github.com/dapr/quickstarts/pull/838/files#diff-ec29a2de731878d2f612e1afb99355da946e3dc2deb31907d55bdc07f981d4f5R117
This also affects us in our mechanical markdown testing and overall test suite reliability.
Release Note
RELEASE NOTE: