Closed ValleJulien closed 8 years ago
Same issue (gzip: stdin: not in gzip format
) here. I had to define v95
in my buildpack file to make it work again.
This is an intermittent issue; it happens when S3 drops the connection mid transfer. No need to revert the buildpack revision. Simply push again and it'll work.
There will be a change in the next buildpack release that catches this error condition and re-tries the transfer.
@srigi I don't know if it could help me to proceed like you suggest, I don't try your suggestion.
In fact, as @dzuelke mentionned in his post, I have to update the buildpack and puh him on to my heroku app.
This issue can be closed, the problem is just to update the buildpack in local and on heroku app.
@dzuelke @ValleJulien Yeah, I realized that this has something with the networking between datacenters. In the morning (in Europe) it worked, around noon it stopped. I had to help myself by this dirty hack because I had to deploy.
Just to clarify, @ValleJulien and @srigi, if this problem occurs, you do not need to take any action other than to redeploy. Changing the buildpack revision has zero impact on the issue, because all buildpack revisions pull from the exact same S3 location (and older revisions may be coded to use tarballs that no longer exist and as such cease to function).
The only thing you need to do is git push heroku master
again, and the build should succeed.
@dzuelke OK, thanks.
Trying to deploy my symfony app I have this error occured:
I really don't understand why, and I am not sure it is in relation with php buildpack. Before this error not appear and I have the same configuration as before.
This is my composer.json file:
For depolying I run this command:
git push heroku my-branch:master
and I see the hroku logs that build the app.More explanation here: http://stackoverflow.com/questions/38523304/deploy-symfony-app-on-heroku-return-push-failed-error
Someone have the same problem ?