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
Updating passed 2014-11-05_06-04-18-ffffab3 causes timeout issue with powershell as a post-update-cmd #3573
Comments
i have some question as follow Fatal error: Uncaught exception 'PharException' with message 'phar "/usr/local/Cellar/composer/1.0.0-alpha9/libexec/composer.phar" has a broken signature' in /usr/local/Cellar/composer/1.0.0-alpha9/libexec/composer.phar:23 |
I see there are 478 open issues so doubtful this will be looked at any time soon |
😞 |
@u01jmg3 could you resolve this somehow? Sorry for the delay getting to this issue but I don't quite see why it should've started to fail. Unfortunately I can hardly try and reproduce it, so it'd be nice if you can update this. |
Tested with
Tested the Powershell command separately so I know it works without error |
That's unfortunate but due to the limited use case here I doubt anyone will look at this. If you'd like to get it fixed it'd be good to dig in yourself a bit, or provide a simpler reproduce case if it really is any powershell command timing out. |
Closing for now.. seems nobody cares enough to fix sorry. |
Shall try and find some time to look at this again and provide more clarity - understand why you have to close it though. |
Yeah I'm not against a fix but I rather avoid issues cluttering the tracker if nobody is interested in fixing them :/ |
composer update
using the most recent version of composer (a422d67e2701860a44a4634f62f88b58b8636468
) causes a timeout error for powershell commands. Has there been a significant change to composer which may be causing this?2014-11-05_06-04-18-ffffab3
is the last version that doesn't suffer from this timeoutThe text was updated successfully, but these errors were encountered: