-
Notifications
You must be signed in to change notification settings - Fork 49
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
ERROR - failed to build #19
Comments
I'm seeing the same thing on the Heroku-20 stack:
|
Yep - same output in my build logs as well. I've removed the build pack for now to move forward. |
Was able to get the buildpack to run by forking, hardcoding to the previous AWS CLI version, and using custom buildpack on Heroku:
I'm assuming something in a recent release is causing bug. |
Same issue here as well. |
Same issue today - identical output |
Same Issue Appearing in Heroku stack-20 aswell. Updates: A new tag has been created to address this issue, as noted in aws/aws-cli#8320. However, the problem still persists for me on Heroku. |
Looks like it might not be used by the awscli latest release yet? since they recommend pinning? |
I just pinned the version to If you want you can use it on heroku |
Thx a lot @deepakmahakale 👊 |
This issue is now fixed. It was not caused by any changes to this buildpack or Heroku, but was instead due to AWS releasing a broken AWS CLI update (v2.13.34) on 10th November, and then unfortunately not fixing it (or rolling back the update) until v2.13.35 released yesterday (three days later). This buildpack installs the latest v2.x version of the AWS CLI, so any upstream changes will be immediately reflected in new builds using this buildpack. Routinely pinning the version of the AWS CLI in this buildpack (and incrementing it as releases occur) just isn't viable given the high rate of releases of the AWS CLI (multiple new releases per week). This buildpack is also not an officially supported buildpack, so is provided on a best effort basis. The bug itself was in |
This build pack is no longer compiling on Heroku stack-22.
Started happening within the past 1-2 hours.
The text was updated successfully, but these errors were encountered: