Max execution time of request on http server about swoole-src HOT 2 OPEN

I used both Swoole & OpenSwoole, and can confirm that both have the same behavior regarding max_execution_time,
one other workaround if you trigger an error, I see that the worker will stop.

ex:
trigger_error('Request timed out', E_USER_ERROR);

but, +1 on this request, I believe this should be handled in Swoole.

from swoole-src.

Problem is, you might have to clean up some connections and whatnot, so if you just stop executing code after the timeout happens in the next context change, you end up with memory leaks and broken code branches and whatnot.

In other words, the $killRequest idea is good, but your code still needs to deal with the cleanup and whatnot.

from swoole-src.