Using exit; in Laravel also stops octane and results in HTTP error 500

[mariandomanik]

• Octane Version: 1.4.2
• Laravel Version: 9.52.4
• PHP Version: 8.1.13
• Server & Version: RoadRunner 2.12.3
• Database Driver & Version: not relevant

Description:

When calling

response()->json([], 200)->send(); exit;

Not only there is no response coming from Laravel response() but the octane worker is also stopped, this is cli output:

`14:53[1015] php artisan octane:start

INFO Server running…

Local: http://127.0.0.1:8000
Press Ctrl+C to stop the server
INFO []
network error
500 GET / ............................. 165.14 ms
worker stopped`

When using exit;, there is always server error with 500. Is this desired? Even calling an empty route with exit; has the same result.

Steps To Reproduce:

Call exit; anywhere in the code and it results to HTTP response 500 and stops the octane worker.

[taylorotwell]

Don't use exit.