-
Notifications
You must be signed in to change notification settings - Fork 522
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
Infracost v0.10.33 being Killed #2882
Comments
Hi! Thanks for creating the issue. Unfortunately, it's pretty hard to debug such issues without the code. Could you please try rerunning it with |
t's really painfull to debug such things in our enterprise environment. The debug logs are very long and I need to relaunch. Code base is large, the default stderr output should be improved |
Maybe the process takes too much memory ? |
This is possible if you have a huge repo. Maybe you'll be able to run this command |
@mapperCoderZ If it makes things easier, we could screenshare. Please drop a message to hello@infracost.io and we'll send a Calendly link to set it up. Thanks! |
@mapperCoderZ just adding to what @vdmgolub mentioned, I think you're already an Infracost Cloud customer - email us and we'll arrange a quick debugging session and get you to success 🚀 |
Hello I have reproduce the case and indeed revert to v31 is a good workaround and we also revert the infracost vscode extension to v20. I try to send to you the whole debug script |
here is the command I launched here is the content of my configuration file: `version: 0.1
you will find the log file attached in this post |
I noticed the same sort of issue in the vscode tasks |
Thanks @matthieupetite, what happens if you run the |
Thanks @matthieupetite, ok a follow up with two questions:
🙏 |
Hi Hugo thanks for your support. I will be able to make that test Monday and I will share the result here |
Hi Hugo, I have test your procedure and with the new version of Infracost and It is failling now |
Hi all, any news on that subject ? |
@matthieupetite we've not got to the bottom of it yet, but it's on our current sprint to investigate further so I will reach out to you sometime in the next 2 weeks. |
thanks a lot |
Hello.
I have an infracost command failing on v0.10.33 but not failing with v0.10.31.
We try to validate our terraform base cost on last version of terraform inside a docker container ARM64 and AMD64. We use azure rm provider.
here is my pipeline logs:
Locally, I have this error without other message:
Killed
Can you have a look ?
The text was updated successfully, but these errors were encountered: