-
Notifications
You must be signed in to change notification settings - Fork 180
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
Stuck on Running 'HashiCorp Terraform' Formatter
#1876
Comments
Running 'HashiCorp Terraform' Formatter
Thank you both for reporting this! This issue may be related to this one: hashicorp/terraform-ls#1857, so downgrading to the previous extension version may be a workaround for now. To confirm a theory, are you by any chance using the AWS provider? |
Thank you for your response, I'll give it a try
Yes, I do |
thanks @dbanck ! Same here, I am using the AWS provider. |
Thanks for the suggestion. I have downgraded to version I use GCP provider. |
Update: Extension |
Same here, so far |
Nah it's still hit and miss. |
Extension Version
v2.33.0
VS Code Version
Version: 1.95.2 (Universal)
Commit: e8653663e8840adaf45af01eab5c627a5af81807
Date: 2024-11-07T11:07:22.054Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.1.0
Operating System
24.1.0 Darwin Kernel Version 24.1.0
Terraform Version
Terraform v1.9.8 on darwin_arm64
Steps to Reproduce
We have a few thousand resources in our state and the extension just never works reliably. I have
"editor.formatOnSave": true,
enabled and whenever I save a file it just hang onRunning 'HashiCorp Terraform' Formatter
Expected Behavior
VSCode Extension works reliably
Actual Behavior
It just hangs
Terraform Configuration
No response
Project Structure
No response
Gist
No response
Anything Else?
Zed Terraform extension works fine and doesn't have this problem. I think it's not a language server issue at least.
Workarounds
No response
References
No response
Help Wanted
Community Note
The text was updated successfully, but these errors were encountered: