Skip to content
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

tflint error encountered while scanning stdout #5253

Closed
1 task done
pfuhrmann opened this issue Feb 11, 2024 · 3 comments
Closed
1 task done

tflint error encountered while scanning stdout #5253

pfuhrmann opened this issue Feb 11, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@pfuhrmann
Copy link

pfuhrmann commented Feb 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

tflint fails due to read error on parallel runs (suspected reason, because on v5 it works).

Expected Behavior

tflint should not fail with the read error.

Super-Linter version

v6.0.0

Relevant log output

22:49:30 [INFO]  go-plugin@v1.6.0/client.go:780: plugin process exited: plugin=/root/.tflint.d/plugins/github.com/terraform-linters/tflint-ruleset-azurerm/0.25.1/tflint-ruleset-azurerm id=11159
  Error: 0 [ERROR] go-plugin@v1.6.0/client.go:804: error encountered while scanning stdout: error="read |0: file already closed"
  22:49:30 [INFO]  go-plugin@v1.6.0/client.go:780: plugin process exited: plugin=/root/.tflint.d/plugins/github.com/terraform-linters/tflint-ruleset-google/0.26.0/tflint-ruleset-google id=11165

Steps To Reproduce

  1. Have a multiple folders with TF configs
  2. Run super-linter in GA
  3. See the log above

Anything else?

@pfuhrmann pfuhrmann added the bug Something isn't working label Feb 11, 2024
@ferrarimarco
Copy link
Collaborator

Hi @pfuhrmann !

Thanks for providing these details. We probably need a few more data points.

Can you please:

  • Share the command that you used to run super-linter locally in order to reproduce the issue?
  • Run super-linter locally with the CREATE_LOG_FILE variable set to true, and attach the log file here so we can have a look?
  • Share a bit more about the structure of your repository (not necessarily the contents, if it's private)? We need this to build a test case to reproduce the issue.

Thanks!

@pfuhrmann
Copy link
Author

pfuhrmann commented Feb 11, 2024

  1. docker run --rm -e RUN_LOCAL=true -e DEFAULT_BRANCH=main -v "$(pwd)":/tmp/lint ghcr.io/super-linter/super-linter:v6.0.0
  2. Sorry, I cannot do that because it would contain sensitive information which I cannot share.
  3. We have a single folder in the repository called terraform which contains ~20 additional folders, each containing HCL files (separate TF states, handling different parts of infrastructure). It's ~10k (HCL) LOC. Please ask for more details if you need to know anything more specific.

With all the above said, this might be not an issue with super-linter. Found out this: hashicorp/go-plugin#298, and it got recently upgraded in tflint: terraform-linters/tflint#1846.

@ferrarimarco
Copy link
Collaborator

Ah! Thanks for the research. That might be it :)

Closing this for now.

@ferrarimarco ferrarimarco closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants