Artisan commands don't terminate the app on SIGINT

[zakini]

Laravel Version

10.13.5

PHP Version

8.2.7

Database Driver & Version

N/A

Description

Stopping an artisan command with CTRL+C (SIGINT) appears to skip gracefully terminating the app, since no registered terminating callbacks are run when this happens.

Since we've got support for handling signals in artisan commands now, this feels like something artisan commands could do out of the box

Steps To Reproduce

1. Clone this example repo: https://github.com/Zakini/artisan-terminating
2. Run php artisan regular - A "Terminating!" message will be in the logs
3. Run php artisan long, then stop it with CTRL+C - No new message will be in the logs
4. Run php artisan long-term, then stop it with CTRL+C - Another "Terminating!" message will be in the logs

[func0der]

Maybe related to this PR? #47725

[func0der]

Especially in development it is problematic, because you can not debug properly that way :D The process does not terminate after you hit the stop button in the IDE for example.

And work is affected if you do use the --once flag instead of the daemon mode.

[ghost]

Good think I never use it.
I use
queue:work;
queue:restart - to clear the cached code;
then again queue:work

[ghost]

Queue:work holds the app bootstrapped in memory just like in laravel octane which causes issues with data clogging etc. Now I'm forced to use queue:listen. Are there any issues with it in laravel 8 and 9 from your knowledge?

[func0der]

@marius-mcp You might want to open another discussion for that, because it unrelated to this issue. :)

[ghost]

@func0der thanks. #49954