/cc @MatTheCat maybe?

Yes I remember it was to avoid memory leaks: #30339

this is because in a non-swoole setup, the profiler does not collect anything in the CLI (as web requests are not handled there) so this avoids memory leaks for long-running commands.

We would need a way to disable that SAPI check for swoole.

How about make a patch like:

     public static function configureLogger(mixed $logger)
     {
-        if (\is_object($logger) && method_exists($logger, 'removeDebugLogger') && \in_array(\PHP_SAPI, ['cli', 'phpdbg'], true)) {
+        if (\is_object($logger) && method_exists($logger, 'removeDebugLogger') && $_ENV['APP_ENV'] === 'prod') {
             $logger->removeDebugLogger();
         }
     }

I patch it locally, and works fine now ( in dev and test environment).

Your proposal has two issues:

• it removes the check on the sapi, which means workers will suffer a memory leak
• Symfony does not enforce any environment name, so you cannot check against one

I don't know much about Swoole, but could you try checking Swoole\Coroutine::getCid() (from swoole/swoole-src#4284 (comment))?

After some testing we could indeed check if Swoole\Coroutine exists and its getCid method returns -1.

But seeing that Roadrunner also leverages the cli SAPI makes me wonder if it really is Symfony’s responsibility to determine whether collecting logs or not 🤔

Hey, thanks for your report!
There has not been a lot of activity here for a while. Is this bug still relevant? Have you managed to find a workaround?

Hello? This issue is about to be closed if nobody replies.

Hey,

I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen!