You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just tried to upgrade to v3.0, and found two issues preventing me from upgrading:
The web server times out when making the opcache:compile request, after 30 seconds. Of course this will vary by each server, but to get around it, I'm forced to use ini_set('maximum_execution_time', 0), which I would rather not do. Is there a better fix that can be made within the package itself for this?
My application is using PHP 7.4. When trying to compile the vendor directory, some packages (e.g. symfony/var-dumper) include test cases for PHP 7.4. When a file with PHP 7.4-specific code tries to compile, the command fails with a 500 error.
I tried excluding the paths, but the exclusion didn't seem to make any difference. Even so, when updating packages, it is feasible more PHP 7.4 code could be added at any time.
I would have thought surrounding the optimisation of each individual file in a try/catch might be a suitable fix?
The text was updated successfully, but these errors were encountered:
I've just tried to upgrade to v3.0, and found two issues preventing me from upgrading:
The web server times out when making the
opcache:compile
request, after 30 seconds. Of course this will vary by each server, but to get around it, I'm forced to useini_set('maximum_execution_time', 0)
, which I would rather not do. Is there a better fix that can be made within the package itself for this?My application is using PHP 7.4. When trying to compile the
vendor
directory, some packages (e.g.symfony/var-dumper
) include test cases for PHP 7.4. When a file with PHP 7.4-specific code tries to compile, the command fails with a 500 error.I tried excluding the paths, but the exclusion didn't seem to make any difference. Even so, when updating packages, it is feasible more PHP 7.4 code could be added at any time.
I would have thought surrounding the optimisation of each individual file in a
try/catch
might be a suitable fix?The text was updated successfully, but these errors were encountered: