Github 上 composer/composer 的最新 issue 回應 https://github.com/composer/composer/issues Github 上 composer/composer 的最新 issue 回應 en-us Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-512334703 I can confirm the same on Docker with centos7 and php 5.4.16. Upping the memory limit to 3 made things work again. https://github.com/composer/composer/issues/8229#issuecomment-512334703 Wed, 17 Jul 2019 23:37:55 +0800 Re: Unable to disable packagist with `composer init` https://github.com/composer/composer/issues/8210#issuecomment-512257068 @stof that I indeed know.<br /> <br /> But I don't want to disable packagist for my entire host system, only for this one (monorepo) project.<br /> So when I do a `composer create-project` within the monorepo to create a new module, I want that command only to ignore packagist.<br /> <br /> When working on a completely different project I am happy to use packagist. https://github.com/composer/composer/issues/8210#issuecomment-512257068 Wed, 17 Jul 2019 21:35:17 +0800 Re: Unable to disable packagist with `composer init` https://github.com/composer/composer/issues/8210#issuecomment-512255343 @Doqnach both commands would respect a setting coming from the global composer config. https://github.com/composer/composer/issues/8210#issuecomment-512255343 Wed, 17 Jul 2019 21:30:59 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-512248318 Even if it ran out of memory, it should end up being killed if that is not allowed. Odd. I would expect some kind of exit of the process to take place. https://github.com/composer/composer/issues/8229#issuecomment-512248318 Wed, 17 Jul 2019 21:13:25 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-512243753 @alcohol Yeah both were running in -vvv mode.<br /> But it seems that it's indeed running out of memory in the standard configuration (2GB) after I bumped it by a good amount it's actually getting to the SAT stage on the container as well<br /> ```<br /> [1756.3MiB/20.20s] Resolving dependencies through SAT<br /> [1756.3MiB/20.20s] <br /> [1756.3MiB/20.20s] Dependency resolution completed in 0.001 seconds<br /> ```<br /> Taking the same ~1.7 GB of memory in that stage.<br /> <br /> I enabled tty in the docker-compose file but I'm not seeing a passes output. https://github.com/composer/composer/issues/8229#issuecomment-512243753 Wed, 17 Jul 2019 21:00:46 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-512240819 Odd, it looks like you get no further output at the SAT solving stage inside the container. This is weird. Are you running in `-vvv` mode? And the container in interactive mode with a tty? It should tell you how many passes it has done so far. https://github.com/composer/composer/issues/8229#issuecomment-512240819 Wed, 17 Jul 2019 20:52:22 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-512239242 @Doqnach I mounted the cache volume and now it does reading only (no more rewriting the cache every time) but it still just stops:<br /> ```<br /> [439.9MiB/4.72s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$web-profiler-bundle.json from cache<br /> [443.3MiB/4.78s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symplify$better-phpdoc-parser.json from cache<br /> [443.8MiB/4.78s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-php-http$client-implementation.json from cache<br /> [445.4MiB/4.82s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$contracts.json from cache<br /> [445.5MiB/4.83s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php56.json from cache<br /> [456.0MiB/4.94s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-util.json from cache<br /> [420.3MiB/5.03s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php54.json from cache<br /> [420.6MiB/5.05s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php70.json from cache<br /> [419.0MiB/5.15s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$icu.json from cache<br /> [421.0MiB/5.24s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$security-acl.json from cache<br /> [421.9MiB/5.28s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$security.json from cache<br /> [422.8MiB/5.36s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-apcu.json from cache<br /> [422.6MiB/5.47s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php55.json from cache<br /> [423.0MiB/5.49s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-ircmaxell$password-compat.json from cache<br /> [422.5MiB/5.69s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-zendframework$zend-stdlib.json from cache<br /> [423.0MiB/5.70s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-athletic$athletic.json from cache<br /> [423.0MiB/5.71s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-zendframework$zend-hydrator.json from cache<br /> [423.4MiB/5.78s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-hoa$core.json from cache<br /> [423.6MiB/5.78s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-hoa$string.json from cache<br /> [425.0MiB/5.92s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-psr$http-client.json from cache<br /> [425.1MiB/5.94s] Reading /tmp/cache/repo/https---repo.packagist.org/provider-nette$schema.json from cache<br /> ```<br /> <br /> Memory usage doesn't really seem that bad I guess though it pushes the CPU pretty hard <br /> <img width="558" alt="Screenshot 2019-07-17 at 14 42 31" src="https://user-images.githubusercontent.com/24696606/61376294-35f59a00-a8a1-11e9-80e3-166a8c17a99f.png"><br /> <br /> Here's the log from the host machine while upgrading:<br /> ```<br /> [447.4MiB/3.68s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-php-http$client-implementation.json from cache<br /> [449.0MiB/3.70s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$contracts.json from cache<br /> [449.0MiB/3.72s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php56.json from cache<br /> [459.5MiB/3.80s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-util.json from cache<br /> [423.9MiB/3.86s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php54.json from cache<br /> [424.2MiB/3.90s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php70.json from cache<br /> [422.6MiB/3.98s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$icu.json from cache<br /> [424.6MiB/4.06s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$security-acl.json from cache<br /> [425.5MiB/4.11s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$security.json from cache<br /> [426.4MiB/4.17s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-apcu.json from cache<br /> [426.2MiB/4.19s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-symfony$polyfill-php55.json from cache<br /> [426.5MiB/4.21s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-ircmaxell$password-compat.json from cache<br /> [426.1MiB/4.40s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-zendframework$zend-stdlib.json from cache<br /> [426.6MiB/4.41s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-athletic$athletic.json from cache<br /> [426.5MiB/4.42s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-zendframework$zend-hydrator.json from cache<br /> [427.0MiB/4.48s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-hoa$core.json from cache<br /> [427.1MiB/4.49s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-hoa$string.json from cache<br /> [428.5MiB/4.60s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-psr$http-client.json from cache<br /> [428.6MiB/4.62s] Reading /Users/kaidederichs/.composer/cache/repo/https---repo.packagist.org/provider-nette$schema.json from cache<br /> [1735.2MiB/15.35s] Resolving dependencies through SAT<br /> [1740.4MiB/15.75s] Looking at all rules.<br /> ```<br /> <br /> I guess it goes up in memory usage quite a lot on the resolving part. https://github.com/composer/composer/issues/8229#issuecomment-512239242 Wed, 17 Jul 2019 20:47:53 +0800 Re: composer.json not writable https://github.com/composer/composer/issues/8232#issuecomment-512223605 Closing because the other issue is pretty much identical and was reported earlier. https://github.com/composer/composer/issues/8232#issuecomment-512223605 Wed, 17 Jul 2019 19:59:55 +0800 Re: composer.json is not readable. https://github.com/composer/composer/issues/8231#issuecomment-512223434 Looks like `is_readable` and `is_writable` might always return `false` when dealing with network drives/shares. Work around as suggested on the issue would be to check for this condition (networked drive/share) and determine through other means if a file is readable or writable. https://github.com/composer/composer/issues/8231#issuecomment-512223434 Wed, 17 Jul 2019 19:59:21 +0800 Re: composer.json not writable https://github.com/composer/composer/issues/8232#issuecomment-512222737 Looks related https://bugs.php.net/bug.php?id=68926 https://github.com/composer/composer/issues/8232#issuecomment-512222737 Wed, 17 Jul 2019 19:57:02 +0800 Re: composer.json is not readable. https://github.com/composer/composer/issues/8231#issuecomment-512222697 Looks related https://bugs.php.net/bug.php?id=68926 https://github.com/composer/composer/issues/8231#issuecomment-512222697 Wed, 17 Jul 2019 19:56:52 +0800 Re: composer.json not writable https://github.com/composer/composer/issues/8232#issuecomment-512221671 Possibly a duplicate of #8231 in terms of issue (potential bug). https://github.com/composer/composer/issues/8232#issuecomment-512221671 Wed, 17 Jul 2019 19:53:23 +0800 Re: FFI and package type considerations https://github.com/composer/composer/issues/8230#issuecomment-512194705 Right you are, did not even think about custom installers. Those would probably be the sanest choice first. https://github.com/composer/composer/issues/8230#issuecomment-512194705 Wed, 17 Jul 2019 18:18:52 +0800 Re: FFI and package type considerations https://github.com/composer/composer/issues/8230#issuecomment-512191445 I think that this is too early to discuss in composer itself, as we don't know yet how a FFI package would look like.<br /> If some special installation is needed for them, this should first be experimented using a dedicated installer developed out of composer (it is much easier to experiment in a third-party installer plugin than in core). And what kind of special installation is needed might even depend on the packages. https://github.com/composer/composer/issues/8230#issuecomment-512191445 Wed, 17 Jul 2019 18:08:24 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-512116657 That is how I share my cache by default. https://github.com/composer/composer/issues/8229#issuecomment-512116657 Wed, 17 Jul 2019 14:08:21 +0800 Re: composer.json is not readable. https://github.com/composer/composer/issues/8231#issuecomment-512116414 I do not do any development on windows machine, so am unable to reproduce this myself. We'll need to find a developer familiar with the source code and access to a windows system to debug this further. https://github.com/composer/composer/issues/8231#issuecomment-512116414 Wed, 17 Jul 2019 14:07:18 +0800 Re: proc_open(NUL): failed to open stream: No such file or directory https://github.com/composer/composer/issues/8152#issuecomment-512061927 The problem is indeed caused by OneDrive. Thank you! https://github.com/composer/composer/issues/8152#issuecomment-512061927 Wed, 17 Jul 2019 09:16:46 +0800 Re: Proc_open (NUL): failed to open stream: No such file or directory https://github.com/composer/composer/issues/7083#issuecomment-512061626 Same problem https://github.com/composer/composer/issues/7083#issuecomment-512061626 Wed, 17 Jul 2019 09:15:10 +0800 Re: Unable to disable packagist with `composer init` https://github.com/composer/composer/issues/8210#issuecomment-511933767 This issue would warrent a "feature" label instead of "support" https://github.com/composer/composer/issues/8210#issuecomment-511933767 Wed, 17 Jul 2019 02:31:42 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-511933525 @KDederichs Try having a host mount for `/tmp/cache` inside the container, from `~/.composer/cache` on the host.<br /> <br /> And run with `--profile` on host and inside container to see if there is a big jump in resource usage, or if the resource usage inside the container is simply bigger than your docker can handle. https://github.com/composer/composer/issues/8229#issuecomment-511933525 Wed, 17 Jul 2019 02:31:00 +0800 Re: [RFC] Preloading support https://github.com/composer/composer/issues/7777#issuecomment-511834583 Guys, preloading requires a ini setting, so Composer won't stab you in the back either way, don't worry ;-) https://github.com/composer/composer/issues/7777#issuecomment-511834583 Tue, 16 Jul 2019 22:14:21 +0800 Re: [RFC] Preloading support https://github.com/composer/composer/issues/7777#issuecomment-511831570 Preload should be disabled by default, and allow a custom list to preload.<br /> That way wouldn't be any problems with ram management in any device.<br /> <br /> El mar., 16 de jul. de 2019 09:07, Otto Rask <notifications@github.com><br /> escribió:<br /> <br /> > Has anyone considered the memory usage on embedded systems where you<br /> > actually do not have gigs and gigs of RAM available? If I want to host a<br /> > small web server on some system that offers a humongous amount of 64<br /> > megabytes of RAM, I can preload like a dozen files and PHP will crap out if<br /> > Composer has decided that "all in" is the best overall preload strategy?<br /> ><br /> > (Somewhat exaggerated example, yes.)<br /> ><br /> > I would say having a preload script generated only from the root project<br /> > composer.json definition, and only with user-defined files is the best<br /> > option, if Composer is to be used for preload file generation at all.<br /> ><br /> > —<br /> > You are receiving this because you commented.<br /> > Reply to this email directly, view it on GitHub<br /> > <https://github.com/composer/composer/issues/7777?email_source=notifications&email_token=ABHHLFYUNB4IWBKM63AFUPTP7XBZJA5CNFSM4GCIOG4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2AZBAQ#issuecomment-511807618>,<br /> > or mute the thread<br /> > <https://github.com/notifications/unsubscribe-auth/ABHHLF3UJX75LEGC7N4IGLLP7XBZJANCNFSM4GCIOG4A><br /> > .<br /> ><br /> https://github.com/composer/composer/issues/7777#issuecomment-511831570 Tue, 16 Jul 2019 22:07:29 +0800 Re: [RFC] Preloading support https://github.com/composer/composer/issues/7777#issuecomment-511807618 Has anyone considered the memory usage on embedded systems where you actually do not have gigs and gigs of RAM available? If I want to host a small web server on some system that offers a humongous amount of 64 megabytes of RAM, I can preload like a dozen files and PHP will crap out if Composer has decided that "all in" is the best overall preload strategy?<br /> <br /> (Somewhat exaggerated example, yes.)<br /> <br /> I would say having a preload script generated only from the root project composer.json definition, and only with user-defined files is the best option, if Composer is to be used for preload file generation at all. https://github.com/composer/composer/issues/7777#issuecomment-511807618 Tue, 16 Jul 2019 21:06:58 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-511760007 This does not change the fact that I cannot reproduce it. We need a reproducible scenario to even begin debugging any potential issues. https://github.com/composer/composer/issues/8229#issuecomment-511760007 Tue, 16 Jul 2019 18:27:27 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-511748738 Here's my docker configuration if that helps:<br /> <br /> Composer container, pretty much the same as the official one but with php 7.3<br /> ```<br /> FROM php:7.3-alpine<br /> <br /> RUN apk add --no-cache --virtual .composer-rundeps git subversion openssh-client mercurial tini bash patch make zip unzip coreutils \<br /> && apk add --no-cache --virtual .build-deps zlib-dev libzip-dev \<br /> && docker-php-ext-configure zip --with-libzip \<br /> && docker-php-ext-install -j$(getconf _NPROCESSORS_ONLN) zip opcache \<br /> && runDeps="$( \<br /> scanelf --needed --nobanner --format '%n#p' --recursive /usr/local/lib/php/extensions \<br /> | tr ',' '\n' \<br /> | sort -u \<br /> | awk 'system("[ -e /usr/local/lib/" $1 " ]") == 0 { next } { print "so:" $1 }' \<br /> )" \<br /> && apk add --no-cache --virtual .composer-phpext-rundeps $runDeps \<br /> && apk del .build-deps \<br /> && printf "# composer php cli ini settings\n\<br /> date.timezone=UTC\n\<br /> memory_limit=-1\n\<br /> opcache.enable_cli=1\n\<br /> " > $PHP_INI_DIR/php-cli.ini<br /> <br /> ENV COMPOSER_ALLOW_SUPERUSER 1<br /> ENV COMPOSER_HOME /tmp<br /> ENV COMPOSER_VERSION 1.8.6<br /> <br /> RUN curl --silent --fail --location --retry 3 --output /tmp/installer.php --url https://raw.githubusercontent.com/composer/getcomposer.org/cb19f2aa3aeaa2006c0cd69a7ef011eb31463067/web/installer \<br /> && php -r " \<br /> \$signature = '48e3236262b34d30969dca3c37281b3b4bbe3221bda826ac6a9a62d6444cdb0dcd0615698a5cbe587c3f0fe57a54d8f5'; \<br /> \$hash = hash('sha384', file_get_contents('/tmp/installer.php')); \<br /> if (!hash_equals(\$signature, \$hash)) { \<br /> unlink('/tmp/installer.php'); \<br /> echo 'Integrity check failed, installer is either corrupt or worse.' . PHP_EOL; \<br /> exit(1); \<br /> }" \<br /> && php /tmp/installer.php --no-ansi --install-dir=/usr/bin --filename=composer --version=${COMPOSER_VERSION} \<br /> && composer --ansi --version --no-interaction \<br /> && rm -f /tmp/installer.php \<br /> && find /tmp -type d -exec chmod -v 1777 {} +<br /> <br /> COPY docker/composer/docker-entrypoint.sh /docker-entrypoint.sh<br /> <br /> WORKDIR /usr/src/app<br /> <br /> ENTRYPOINT ["/bin/sh", "/docker-entrypoint.sh"]<br /> ```<br /> <br /> And the one for my app<br /> <br /> ```<br /> # ./docker/php/Dockerfile<br /> FROM php:7.3-fpm<br /> <br /> RUN usermod -u 1000 www-data<br /> RUN groupmod -g 1000 www-data<br /> <br /> RUN apt-get update -qq && apt-get install -y -qq \<br /> libfreetype6-dev \<br /> libjpeg62-turbo-dev \<br /> libmcrypt-dev \<br /> git \<br /> zlib1g-dev libicu-dev g++ \<br /> wget libpq-dev libzip-dev unzip<br /> <br /> RUN docker-php-ext-install -j$(nproc) iconv bcmath intl zip opcache pdo_mysql\<br /> && docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ \<br /> && docker-php-ext-install -j$(nproc) gd \<br /> && docker-php-ext-enable opcache<br /> <br /> RUN pecl install apcu-5.1.17<br /> RUN pecl install redis<br /> RUN docker-php-ext-enable apcu<br /> RUN docker-php-ext-enable redis<br /> <br /> RUN curl -s https://getcomposer.org/composer.phar > /usr/local/bin/composer \<br /> && chmod a+x /usr/local/bin/composer<br /> <br /> COPY docker/php/ini/99opcache.ini /usr/local/etc/php/conf.d/99opcache.ini<br /> <br /> WORKDIR /var/www/app<br /> <br /> COPY apps/my_app /var/www/app<br /> <br /> RUN PATH=$PATH:/var/www/app/vendor/bin:bin<br /> <br /> RUN if [ -e vendor/composer ]; then composer install --optimize-autoloader --apcu-autoloader; fi<br /> <br /> <br /> RUN if [ -e vendor/composer ]; then chown -R www-data:www-data vendor/composer vendor/*.php config public var bin; fi<br /> RUN if [ -e vendor/composer ]; then chown -R www-data:www-data /var/www; fi<br /> USER www-data<br /> ```<br /> <br /> everything is glued together using docker-compose and docker-sync:<br /> (shorter version of compose file, omitting stuff like mysql etc that's not relevant here)<br /> ```<br /> version: '3.7'<br /> services:<br /> php:<br /> build:<br /> context: .<br /> dockerfile: docker/php/Dockerfile<br /> restart: on-failure<br /> env_file:<br /> - .env<br /> volumes:<br /> - 'app-sync:/var/www/app:nocopy'<br /> composer:<br /> build:<br /> context: .<br /> dockerfile: docker/composer/Dockerfile<br /> volumes:<br /> - 'app-sync:/var/www/app:nocopy'<br /> working_dir: /var/www/app<br /> stdin_open: true<br /> tty: true<br /> environment:<br /> - COMPOSER_MEMORY_LIMIT=-1<br /> ``` https://github.com/composer/composer/issues/8229#issuecomment-511748738 Tue, 16 Jul 2019 17:52:41 +0800 Re: Cannot update packages anymore "Fatal error: Out of memory (allocated 1392771072) (tried to allocate 268435456 bytes)" https://github.com/composer/composer/issues/7348#issuecomment-511726928 You may also get resolved by just removing vendor directory and re-execute composer install command. https://github.com/composer/composer/issues/7348#issuecomment-511726928 Tue, 16 Jul 2019 16:50:51 +0800 Re: Composer not working correctly in container? https://github.com/composer/composer/issues/8229#issuecomment-511700627 Cannot reproduce. https://github.com/composer/composer/issues/8229#issuecomment-511700627 Tue, 16 Jul 2019 15:30:19 +0800 Re: Windows (WSL): ErrorException on composer update: proc_open(): fork failed - Invalid argument https://github.com/composer/composer/issues/8135#issuecomment-511446345 I have already learned the reason for this problem. It was a problem with missing RAM memory.<br /> Recent updates of Windows and Chrome have increased memory requirements. Composer consumed over 1GB at the peak and the system had to kill it. I have an swap file turned off.<br /> I have increased the amount of memory and I do not have this problem anymore.<br /> https://github.com/composer/composer/issues/8135#issuecomment-511446345 Mon, 15 Jul 2019 23:19:39 +0800 Re: dump-autoload command wants to download https://flex.symfony.com/versions.json https://github.com/composer/composer/issues/8227#issuecomment-511359498 But you should not run Composer on a production system. You should create a production ready build artifact in your pipeline and release/deploy that instead. https://github.com/composer/composer/issues/8227#issuecomment-511359498 Mon, 15 Jul 2019 19:06:13 +0800 Re: dump-autoload command wants to download https://flex.symfony.com/versions.json https://github.com/composer/composer/issues/8227#issuecomment-511359275 Include `--no-scripts` https://github.com/composer/composer/issues/8227#issuecomment-511359275 Mon, 15 Jul 2019 19:05:24 +0800