New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
composer why-not produces LogicException (ProcessExecutor) similar to #10703 #10783
Comments
which exact version of composer are you using ? |
What it says in the |
Do you have a path repository configured in your global composer config ? Otherwise, I don't see why a PathRepository would try to initialize. |
Yes I have:
|
Seldaek
added a commit
to Seldaek/composer
that referenced
this issue
May 24, 2022
…e, and make sure async is always enabled on the process executor, fixes composer#10783
Seldaek
added a commit
to Seldaek/composer
that referenced
this issue
May 24, 2022
…e, and make sure async is always enabled on the process executor, fixes composer#10783
emahorvat52
pushed a commit
to emahorvat52/composer
that referenced
this issue
Feb 3, 2023
…e, and make sure async is always enabled on the process executor, fixes composer#10783 (composer#10799)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have almost the same problem as described in #10703 but with Composer command "why-not".
Last known good: 2.2.9
Broken since: 2.3.0
My
composer.json
:Output of
composer diagnose
:When I run this command:
I get the following output:
And I expected this to happen:
The text was updated successfully, but these errors were encountered: