php-cli | php command line / cli scritping and coloring classes | Command Line Interface library

I solve the issue by not writing the opcache.preload stuff into the php.ini directly, but to use a command in the Dockerfile to patch the php.ini after the container installed php and additional extensions correctly:

You should follow the OAuth Flow for Web applications. There is a difference in the credentials object, and the token would be stored in the session, meaning you don't have to copy and paste it into a terminal.

• https://github.com/googleapis/google-api-php-client/blob/master/examples/simple-file-upload.php

• https://developers.google.com/identity/protocols/oauth2/web-server
• https://github.com/googleapis/google-api-php-client/blob/master/README.md#authentication-with-oauth

If you are using php-fpm, you can use php-fpm -i | grep php.ini to find the loaded configuration file.

If using php-cli, php -i | grep php.ini, and so on.

On some occasions, php-fpm and php-cli aren't using the same php.ini.

php -i -> php-cli

php-fpm -i -> php-fpm

Then add extension=yourExtension.so to php.ini, and restart your php-fpm, using php-fpm -m | grep yourExtension to check if the extension is loaded, it means work if printed you extension name.

If there's not, then, you need to find the extension_dir of php : php-fpm -i | grep extension_dir, and check if there is yourExtension.so file, if there's not, it means your extension installed to a wrong place, you need make a soft link or simply cp yourExtension.so to that place.

If you're using multi-version php, you need check which php you are using.

I confirmed that in the case of your script, in order to retrieve the parent folder ID, $file2 = $this->drive->files->get($fileId) is used. When you are using Drive API v3, the values of kind, name, id and mimeType are returned as the default response values. It seems that this is the current specification. I thought that the reason of your issue might be due to this.

If my understanding is correct, how about the following modification?

I believe that the asterisk is interpreted by the shell, did you try yum -y remove 'php*'?

The problem solved just by deleting the /etc/php.d/ directory. Then reinstall PHP.

Refering to the PHP manual the unit for megabyte is M, not MB.

So you should set it to

Yeah, GitHub's cache action has unintuitive behavior across branches. Pull request workflows don't share, and tag workflows never get a cache hit.

Per the docs (useful bit made bold):

A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually main). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch feature-b has the base branch feature-a, a workflow triggered on feature-b would have access to caches created in the default branch (main), feature-a, and feature-b.

So the solution then is to make a separate workflow triggered by pushes to main — plus any base branches you like — just to keep a fresh cache available to pull requests and tags.

Your installation seems a mess

1/ 2 PHP Stacks

You have both PHP 7.4 (php-* packages) and 7.3 installed (php73-php-* packages)

Read: Difference between php-* and php##-php-* packages ?

I recommend you remove everything