-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Panic in Terraform console command #33195
Comments
Thanks for this report! |
I took a look into this and I think it might actually be a bug from the ReadLine library. I'm seeing they have a very similar problem on exiting the console in this issue here. Edit: After a closer look I think this is just an issue with ReadLine, which is getting called in (and crashing) from the console. |
Seems like perfect timing. @crw, could you please assess if chzyer/readline can be swapped out for a maintained fork - ergochat/readline? |
Hi, I'm one of the ergochat/readline maintainers and I'm very interested in seeing if our fork is suitable for use in terraform! From my initial investigation:
|
I opened a PR for this: ergochat/readline#33 |
I released the previously mentioned fix, released it as v0.0.5, and wrote a draft PR for Terraform that switches to ergochat/[email protected]: #33305 |
Thanks for this information and the pull request! The question of changing / updating dependencies is being run past the security team. We appreciate the background and info on these libraries! |
Terraform Version
Terraform Configuration Files
No config files required
Debug Output
https://gist.github.com/pcarles/da14c26485822361018252868c66e62f
Expected Behavior
Terraform should exit gracefully
Actual Behavior
Terraform panic with a segfault
Steps to Reproduce
terraform console
anywhereAdditional Context
You don't need any configuration file to reproduce this error, and doing it with configuration files present do not change the behavior, it seems to be consistent.
I may open a PR to to fix it when I have a bit of time
References
No response
The text was updated successfully, but these errors were encountered: