`max_execution_time` config doesn't work

[smortexa]

• Octane Version: 1.1.1
• Laravel Version: 8.77.1
• PHP Version: 8.1.0
• Server & Version: Swoole 4.8.3

Description:

When the execution time for requests being handled by Octane exceeded from max_execution_time in octane.php config file, the Octane wouldn't send any response and the request remains in the pending state.

Steps To Reproduce:

Set max_execution_time to 2 seconds in octane.php:

// config/octane.php
return [
    'max_execution_time' => 2,
];

and try:

Route::get('/foo', function() {
    sleep(3);
    return 'bar';
});

I know this may be a Swoole bug. So if confirmed, I'll open an issue on the Swoole repo.

[sy-records]

When the max_execution_time is reached, it is a SIGKILL signal sent directly, so it causes no response.

octane/src/Swoole/Actions/EnsureRequestsDontExceedMaxExecutionTime.php

Line 27 in 722b756

$this->extension->dispatchProcessSignal($row['worker_pid'], SIGKILL);

This is not a bug, but require Swoole support.
OpenSwoole add a max_request_execution_time.

[driesvints]

Thanks @sy-records

[smortexa]

@sy-records The Swoole maintainer solution also doesn't work. The following error will be thrown:

PHP Fatal error:  Uncaught ErrorException: Swoole\Http\Response::status(): http response is unavailable (maybe it has been ended or detached)