Github 上 composer/composer 的最新 issue 回應 https://github.com/composer/composer/issues Github 上 composer/composer 的最新 issue 回應 en-us Re: Composer hangs on simplest command https://github.com/composer/composer/issues/8109#issuecomment-486412282 Cannot reproduce. https://github.com/composer/composer/issues/8109#issuecomment-486412282 Thu, 25 Apr 2019 04:26:53 +0800 Re: Composer v2: Pool/Solver/Repo/Installer Tasks https://github.com/composer/composer/issues/7630#issuecomment-486394842 > Is this a joke of some sort? You want people to install some obscure PHP extension to be able to use Composer?<br /> <br /> The performance of composer is a joke, people are going to be upset and will also start to reach out for any possible solution. I suspect a lot of people would happily install an obscure extension than endure the CPU/RAM consumption as well as the waiting.<br /> <br /> If compression is being proposed for just speeding up downloading of package lists, then make that capabilities based and negotiate, though I pity the fool that only has the xml extension loaded.<br /> <br /> If you've got a CDN or proxy layer or something then that can store those, you have control over that so you can make sure it has a good range of serializers and compression.<br /> <br /> Composer could check for available serializers and compression routines then select the best. Use accept and accept encoding and just let the HTTP server choose for you.<br /> https://github.com/composer/composer/issues/7630#issuecomment-486394842 Thu, 25 Apr 2019 03:34:48 +0800 Re: Fixes #8065: Sort plugins deterministically before loading. https://github.com/composer/composer/pull/8085#issuecomment-486274319 I opened https://github.com/composer/composer/pull/8108 as a simpler alternative to this if you think that would be easier to review. https://github.com/composer/composer/pull/8085#issuecomment-486274319 Wed, 24 Apr 2019 22:48:47 +0800 Re: Can not install composer if php 7.3 https://github.com/composer/composer/issues/8046#issuecomment-486140785 Same issue. Any news? https://github.com/composer/composer/issues/8046#issuecomment-486140785 Wed, 24 Apr 2019 17:20:55 +0800 Re: Fixes #8065: Sort plugins deterministically before loading. https://github.com/composer/composer/pull/8085#issuecomment-485971882 @Seldaek would you mind taking another look? This has been a long and ugly problem for downstream projects with no other viable workaround, I'd love to get this (or any other solution) merged soon. https://github.com/composer/composer/pull/8085#issuecomment-485971882 Wed, 24 Apr 2019 04:58:30 +0800 Re: COMPOSER_AUTH environment variable is malformed, should be a valid JSON object https://github.com/composer/composer/issues/8106#issuecomment-485817553 Hello good Morning<br /> <br /> Perhaps the occurrence is related to the EBS,<br /> <br /> Thank you for interacting and sorry for anything. https://github.com/composer/composer/issues/8106#issuecomment-485817553 Tue, 23 Apr 2019 22:05:11 +0800 Re: COMPOSER_AUTH environment variable is malformed, should be a valid JSON object https://github.com/composer/composer/issues/8106#issuecomment-485681574 The error explains itself. Not really sure what you want us to tell you. Perhaps the contents of the environment variable is escaped too many times (or not enough)? https://github.com/composer/composer/issues/8106#issuecomment-485681574 Tue, 23 Apr 2019 15:42:30 +0800 Re: Your requirements could not be resolved to an installable set of packages https://github.com/composer/composer/issues/8105#issuecomment-485597676 Looks like the clone you made interferes with using it in your project. The message you get is that you have contradicting requirements. It wants to get 3.3.0 for you but there is something already requiring dev-develop. Composer can only use one version in a project at the time. Not sure, but suspect you are running this from the clone. You should run it from the project you want to start. No need for cloning, composer will make it available for you. https://github.com/composer/composer/issues/8105#issuecomment-485597676 Tue, 23 Apr 2019 08:25:32 +0800 Re: preg_match(): JIT compilation failed: no more memory https://github.com/composer/composer/issues/7836#issuecomment-485447739 FYI - This also helped to correct (Thanks to @NickWilde1990 for the pointer!)<br /> <br /> ```<br /> [RuntimeException]<br /> Failed to execute regex: PREG_JIT_STACKLIMIT_ERROR<br /> ```<br /> <br /> with <br /> <br /> * COMPOSER 1.8.5<br /> * PHP 7.3.2<br /> * OSX 10.14.3 (Mojave) https://github.com/composer/composer/issues/7836#issuecomment-485447739 Mon, 22 Apr 2019 23:21:01 +0800 Re: Using YAML for configuration? https://github.com/composer/composer/issues/440#issuecomment-485443158 [another one][1]. a fork of [gorw/composer-yaml][2] with [example scripts][3] for composer, yarn and box. i am using yaml over json many times. <br /> <br /> [1]: https://gitlab.com/c33s-group/yaml-convert/blob/master/README.md<br /> [2]: https://github.com/igorw/composer-yaml <br /> [3]: https://gitlab.com/c33s-group/yaml-convert/tree/master/bin https://github.com/composer/composer/issues/440#issuecomment-485443158 Mon, 22 Apr 2019 23:04:08 +0800 Re: Using YAML for configuration? https://github.com/composer/composer/issues/440#issuecomment-485391066 A slightly different approach: https://github.com/sandfoxme/composer-yaml<br /> A wrapper command that allows composer to use yaml config directly instead of explicit conversion https://github.com/composer/composer/issues/440#issuecomment-485391066 Mon, 22 Apr 2019 18:55:11 +0800 Re: Your requirements could not be resolved to an installable set of packages https://github.com/composer/composer/issues/8105#issuecomment-485270710 Can you please show the contents of your `composer.json` file? https://github.com/composer/composer/issues/8105#issuecomment-485270710 Mon, 22 Apr 2019 02:00:16 +0800 Re: Feature suggestion: composer outdated advanced https://github.com/composer/composer/issues/8104#issuecomment-485251713 As @localheinz pointed out. At least a link to the diff with the version tags is not quite "out of scope".<br /> Since this is the point of `composer outdated` to see what packages are outdated and what might have changed. Also the complexity is not really high with that one.<br /> <br /> Sure the full suggestion might be a bit over the top here. But as I said, the spec it self is what we can change and discus here :)<br /> <br /> And no. Unfortunately `composer update --dry-run` does not work. https://github.com/composer/composer/issues/8104#issuecomment-485251713 Sun, 21 Apr 2019 21:26:14 +0800 Re: SHA384 is not supported by your openssl extension, https://github.com/composer/composer/issues/7802#issuecomment-485244508 Hi, I have a different kind of problem. Lately I got a new laptop and I tried to install composer but the same message keep appearing and interrupt the setup causing it to cancel the process.<br /> This is the message that appear :<br /> "SHA384 is not supported by your openssl extension composer"<br /> Please help me, guys https://github.com/composer/composer/issues/7802#issuecomment-485244508 Sun, 21 Apr 2019 19:33:36 +0800 Re: Composer hangs in "Something's changed, looking at all rules again" state https://github.com/composer/composer/issues/7665#issuecomment-484930557 So, 6 hours later I have my `composer update` working again.<br /> <br /> I can't say for sure how I fixed it but it appears that 2 requirements (1 from the main project and the other one from a private package) conflicted with each other, same package but different version constraint (so it's actually a single requirement but is listed in 2 composer.json files). This did not resulted in an error from composer telling me about this conflict but just an endless loop of retries. The only reason I discovered this issue was because I gave up and reverted the updated version constraint of the package in the main project. I was planning to work on it again in the following week but decided to just try and remove this requirement from my main project since 1 requirement should be enough, and this worked.... https://github.com/composer/composer/issues/7665#issuecomment-484930557 Fri, 19 Apr 2019 23:25:34 +0800 Re: Composer hangs in "Something's changed, looking at all rules again" state https://github.com/composer/composer/issues/7665#issuecomment-484803592 I'm having the same issue in which composers hangs for no obvious reason. When I asked someone else to run `composer update` (same project and branch) he very quickly got an error about conflicting packages. It was surprising to me that I did not get this error and already was on attempt 550 while he got the error within seconds. We are running a same setup, same composer version, same PHP version, same OS(X) etc.<br /> <br /> After resolving the conflict (which originated in a private package) I was hoping to be able to run the update but was surprised to see that both our composers are now are retrying....<br /> <br /> When you look at [Solver.php line 770](https://github.com/composer/composer/blob/0619fbed58c1a8e07ab7529fa6f09a378c82ec94/src/Composer/DependencyResolver/Solver.php#L770) you will see the conditions in which this loops pops up. In the comments provided from line 627 to 678 there is some interesting information: "if we encounter a problem, we rewind to a safe level and restart with step 1". <br /> <br /> It seems to be looping for a very long time **unless** you remove _composer.lock_. After I removed it I received new errors about conflicting packages.<br /> https://github.com/composer/composer/issues/7665#issuecomment-484803592 Fri, 19 Apr 2019 16:14:47 +0800 Re: Unable to download & install laravel with composer https://github.com/composer/composer/issues/5656#issuecomment-484756926 Hello Frirnds,<br /> I am getting this error while installing laravel by composer by cmd<br /> <br /> [Composer\Downloader\TransportException]<br /> Content-Length mismatch, received 1490135 bytes out of the expected 2080224<br /> <br /> <br /> create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--r<br /> epository REPOSITORY] [--repository-url REPOSITORY-URL] [--dev] [--no-dev] [--no<br /> -custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vc<br /> s] [--remove-vcs] [--no-install] [--ignore-platform-reqs] [--] [<package>] [<dir<br /> ectory>] [<version>]<br /> <br /> <br /> So anyone can tell the solution<br /> <br /> i used following command to install laravel<br /> <br /> composer create-project laravel/laravel laravel "5.1.*"<br /> <br /> Please Help me...<br /> https://github.com/composer/composer/issues/5656#issuecomment-484756926 Fri, 19 Apr 2019 11:32:19 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484441373 I think I found the problem, it is my fault, one of my .so has gone wrong, solved, thanks all of you. https://github.com/composer/composer/issues/8103#issuecomment-484441373 Thu, 18 Apr 2019 18:23:07 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484439573 Please give the full output of `php -i`, not just one line of it. https://github.com/composer/composer/issues/8103#issuecomment-484439573 Thu, 18 Apr 2019 18:16:33 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484439215 > And what was the output of `type composer`?<br /> > What about `which php`? And `type php`?<br /> > And the output of `php --ini` and `php -i`?<br /> <br /> which php<br /> /usr/bin/php<br /> <br /> php --ini<br /> Configuration File (php.ini) Path: /etc<br /> Loaded Configuration File: /etc/php.ini<br /> Scan for additional .ini files in: /etc/php.d<br /> Additional .ini files parsed: /etc/php.d/bcmath.ini,<br /> ...<br /> <br /> short_open_tag = On<br /> https://github.com/composer/composer/issues/8103#issuecomment-484439215 Thu, 18 Apr 2019 18:15:14 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484438960 > Also, what if you just do this for a moment:<br /> > <br /> > ```<br /> > cd $(mktemp -d)<br /> > wget https://getcomposer.org/download/1.8.5/composer.phar<br /> > php composer.phar --version<br /> > ```<br /> <br /> PHP Warning: Unexpected character in input: ' in phar:///tmp/tmp.oWLx3XentV/composer.phar/bin/composer on line 62<br /> <br /> I was wondering if it would be my PHP environment problem, but other applications on my website are running normally. https://github.com/composer/composer/issues/8103#issuecomment-484438960 Thu, 18 Apr 2019 18:14:17 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484437321 Also, what if you just do this for a moment:<br /> <br /> ```<br /> cd $(mktemp -d)<br /> wget https://getcomposer.org/download/1.8.5/composer.phar<br /> php composer.phar --version<br /> ``` https://github.com/composer/composer/issues/8103#issuecomment-484437321 Thu, 18 Apr 2019 18:08:22 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484436391 And what was the output of `type composer`?<br /> What about `which php`? And `type php`?<br /> And the output of `php --ini` and `php -i`? https://github.com/composer/composer/issues/8103#issuecomment-484436391 Thu, 18 Apr 2019 18:05:10 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484436207 > > Installation step:<br /> > > php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"<br /> > > php -r "if (hash_file('sha384', 'composer-setup.php') === '48e3236262b34d30969dca3c37281b3b4bbe3221bda826ac6a9a62d6444cdb0dcd0615698a5cbe587c3f0fe57a54d8f5') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"<br /> > > php composer-setup.php<br /> > > php -r "unlink('composer-setup.php');"<br /> > > which composer:<br /> > > /usr/local/bin/composer<br /> > > Flollow error is returned when I run the composer command:<br /> > > PHP Warning: Unexpected character in input: ' in phar:///usr/local/bin/composer/bin/composer on line 62<br /> > <br /> > Hi, I feel like you should send out how you use the composer command line and use the -v option<br /> <br /> Executing composer -v will also get this error. https://github.com/composer/composer/issues/8103#issuecomment-484436207 Thu, 18 Apr 2019 18:04:30 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484435502 Sorry, I missed a step, I executed sudo mv composer.phar /usr/local/bin/composer. https://github.com/composer/composer/issues/8103#issuecomment-484435502 Thu, 18 Apr 2019 18:02:03 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484435347 > Installation step:<br /> > php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"<br /> > php -r "if (hash_file('sha384', 'composer-setup.php') === '48e3236262b34d30969dca3c37281b3b4bbe3221bda826ac6a9a62d6444cdb0dcd0615698a5cbe587c3f0fe57a54d8f5') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"<br /> > php composer-setup.php<br /> > php -r "unlink('composer-setup.php');"<br /> > which composer:<br /> > /usr/local/bin/composer<br /> > <br /> > Flollow error is returned when I run the composer command:<br /> > PHP Warning: Unexpected character in input: ' in phar:///usr/local/bin/composer/bin/composer on line 62<br /> <br /> Hi, I feel like you should send out how you use the composer command line and use the -v option https://github.com/composer/composer/issues/8103#issuecomment-484435347 Thu, 18 Apr 2019 18:01:32 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484434872 That does not make much sense.<br /> <br /> The installer will deliver a `composer.phar` in your current directory. You are executing a binary called `composer`. These are two very different files.<br /> <br /> It is rather difficult to help you if you do not know what you are doing to begin with. https://github.com/composer/composer/issues/8103#issuecomment-484434872 Thu, 18 Apr 2019 17:59:56 +0800 Re: Unable to run composer https://github.com/composer/composer/issues/8103#issuecomment-484431960 Installation step:<br /> php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"<br /> php -r "if (hash_file('sha384', 'composer-setup.php') === '48e3236262b34d30969dca3c37281b3b4bbe3221bda826ac6a9a62d6444cdb0dcd0615698a5cbe587c3f0fe57a54d8f5') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"<br /> php composer-setup.php<br /> php -r "unlink('composer-setup.php');"<br /> which composer:<br /> /usr/local/bin/composer<br /> <br /> Flollow error is returned when I run the composer command:<br /> PHP Warning: Unexpected character in input: ' in phar:///usr/local/bin/composer/bin/composer on line 62<br /> https://github.com/composer/composer/issues/8103#issuecomment-484431960 Thu, 18 Apr 2019 17:50:22 +0800 Re: Feature suggestion: composer outdated advanced https://github.com/composer/composer/issues/8104#issuecomment-484421557 Have you tried running the mentioned plugin with an update in dry-run mode btw? I do not know if that process still provides sufficient information for the plugin to determine the changes etc, but if it does, that would reduce the need to revert any changes. https://github.com/composer/composer/issues/8104#issuecomment-484421557 Thu, 18 Apr 2019 17:16:56 +0800 Re: Feature suggestion: composer outdated advanced https://github.com/composer/composer/issues/8104#issuecomment-484420034 I think this is a problem that plugins can solve perfectly. This does not belong in Composer core IMHO. Way too complex and completely out of scope. https://github.com/composer/composer/issues/8104#issuecomment-484420034 Thu, 18 Apr 2019 17:11:56 +0800