Skip to content
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

Closed
u01jmg3 opened this issue Dec 19, 2014 · 9 comments
Labels
Milestone

Comments

@u01jmg3
Copy link

u01jmg3 commented Dec 19, 2014

  • I am finding that running 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 timeout
"post-update-cmd": [
    "php artisan clear-compiled",
    "php artisan debugbar:publish",
    "php artisan optimize",
    "powershell -Command \"(gc vendor/laravel/framework/src/Illuminate/View/Environment.php) -replace '\\$mergeData, \\$this', '(array)$mergeData, (array)$this' | Out-File -encoding ASCII vendor/laravel/framework/src/Illuminate/View/Environment.php\""
]
@ruikc
Copy link

ruikc commented Dec 22, 2014

i have some question as follow
PHP 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
Stack trace:
#0 /usr/local/Cellar/composer/1.0.0-alpha9/libexec/composer.phar(23): Phar::mapPhar('composer.phar')
#1 {main}
thrown in /usr/local/Cellar/composer/1.0.0-alpha9/libexec/composer.phar on line 23

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
Stack trace:
#0 /usr/local/Cellar/composer/1.0.0-alpha9/libexec/composer.phar(23): Phar::mapPhar('composer.phar')
#1 {main}
thrown in /usr/local/Cellar/composer/1.0.0-alpha9/libexec/composer.phar on line 23

@u01jmg3
Copy link
Author

u01jmg3 commented Apr 8, 2015

I see there are 478 open issues so doubtful this will be looked at any time soon

@u01jmg3
Copy link
Author

u01jmg3 commented May 12, 2015

2014-11-05_06-04-18-ffffab3 is now too old to run so there is no working copy of composer I can use with the post-update-cmd above

😞

@Seldaek
Copy link
Member

Seldaek commented Nov 19, 2015

@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.

@Seldaek Seldaek added the Bug label Nov 19, 2015
@Seldaek Seldaek added this to the Bugs milestone Nov 19, 2015
@u01jmg3
Copy link
Author

u01jmg3 commented Jan 7, 2016

Tested with 64b0d721838cdceef679761c5cf69a0d070d14c9 and still getting a timeout trying to run the following as a post-update-cmd:

powershell -Command "(gc vendor/laravel/framework/src/Illuminate/View/Environment.php) -replace '\$mergeData, \$this', '(array)$mergeData, (array)$this' | Out-File -encoding ASCII vendor/laravel/framework/src/Illuminate/View/Environment.php"

Tested the Powershell command separately so I know it works without error

@Seldaek
Copy link
Member

Seldaek commented Apr 15, 2016

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.

@Seldaek
Copy link
Member

Seldaek commented Mar 7, 2017

Closing for now.. seems nobody cares enough to fix sorry.

@Seldaek Seldaek closed this as completed Mar 7, 2017
@u01jmg3
Copy link
Author

u01jmg3 commented Mar 7, 2017

Shall try and find some time to look at this again and provide more clarity - understand why you have to close it though.

@Seldaek
Copy link
Member

Seldaek commented Mar 7, 2017

Yeah I'm not against a fix but I rather avoid issues cluttering the tracker if nobody is interested in fixing them :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants