-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/tools/imports: should not scan bazel-out directories #35914
Comments
Thank you for filing a gopls issue! Please take a look at the Troubleshooting guide, and make sure that you have provided all of the relevant information here. |
I assume goimports behaves the same way, so retitling. We don't currently support |
Concretely, I'd suggest that the main module, and any replace targets, could contain a @vincepri, would that work for you as well? It would mean checking in a bunch of |
I just commented in the other closed issue, but this is also relevant for this one I believe: #30058 (comment) |
For now, the workaround that we will probably have to do for our monorepo is to move our top-level I think for multi-language repositories having some way to ignore certain directories by all go tools is a must have! The case of node_modules was discussed multiple times in many different issues, but seems like people were unable to agree on a solution. @robpike didn't want to create more dot files, so being able to configure this in |
@heschik Thanks a lot for the clarification! I will try to submit a proposal for a global ignore mechanism for all the Go ecosystem. |
Shall this one be closed in favor of #42473 then? It seems to be more general. |
Because this is no longer assigned, it popped back into my wheelhouse. Given that #42473 is closed, should this be closed as well? Marking as NeedsDecision. |
No, this is a separate issue. |
What did you do?
Open our monolith repository in VS Code, then open a go file and wait.
What did you expect to see?
Nothing.
What did you see instead?
The CPU usage goes up periodically due to gopls.
Build info
Go info
VSCode settings
Relevant logs
More Info
By inspecting the file opened by
gopls
, it's scanning bazel-out.The text was updated successfully, but these errors were encountered: