Timer::tick prevents server from stopping. SIGTERM is getting ignored about swoole-src HOT 5 CLOSED

Okay, but when i add Timer in my server, it cant be stopped gracefully. It delays deployments etc. Can this be fixed on your side? Can you guys add logic to kill every timer when SIGTERM received?

from swoole-src.

I thought i can register some event/signal handler, and then call Timer::clearAll(), but i had no success.

Tried Process\signal:

\Swoole\Process::signal(SIGTERM, function () {
            var_dump('sigterm!');
            Timer::clearAll();
        });

received this warning:

Warning: Swoole\Process::signal(): signal [15] processor has been registered by the system in /app.php on line 18

... and callback is never executed

$server->on('shutdown') is not triggered in my case too.

from swoole-src.

In Swoole\Server, it is not possible to set certain signal listeners, such as SIGTERM and SIGALAM.

from swoole-src.

@zip-fa You should listen to the workerExit event and perform cleanup in this event callback

$serv = new Swoole\Server("0.0.0.0", 9501);

$serv->on('WorkerExit', function ($serv, $workerId){
	$this->cleanup();
});

$serv->start();

from swoole-src.

This doesn't resolve my issue, since i have specific code and workerExit is not suitable.
Even if i move my code, Timer::tick() issue will not be resolved. Can this be reopened? @matyhtf

from swoole-src.