Closed fritzmg closed 6 years ago
The contao-manager uses a default timeout of 500
seconds for example for its Symfony\Component\Process\Process
es as far as I can see: https://github.com/terminal42/background-process/blob/master/src/Forker/AbstractForker.php#L28
/cc @aschempp
This continues to be a problem for us on in some hosting environments. Could the timeout please be increased to 500
in Contao 4.4.15
and 4.5.5
?
Same issue here when running Contao 4.4 managed edition in a Docker container. I was able to workaround this issue by adding an explicit timeout limit $process->setTimeout(2000);
at vendor/contao/manager-bundle/src/Composer/ScriptHandler.php:executeCommand(...) like the image shows below.
I think it would be nice if these processes honor the COMPOSER_PROCESS_TIMEOUT environment variable.
Fixed in df75e0381fddd3f505e8adb982c5650c8502954c.
The manager-bundle uses
Symfony\Component\Process\Process
inScriptHandler::executeCommand
. Its default timeout is60
seconds. However, in some environments warming the cache can take a long time and thus the execution of this command ends with an exception:See also https://community.contao.org/de/showthread.php?68815-gelöst-Contao-Manager-bricht-ab-(Timeout). There are a few more reported instances. They happen especially when the Contao Manager is in use.