Closed ahmedyarub closed 4 months ago
ahmedyarub
commented
4 months ago I could fix it by reverting this line https://github.com/bazelbuild/intellij/commit/b7b5ac6046bfe43ea5f0c032ad0cf0f15f28ea9c#diff-02de1d11ce569be6f82be2a91441d7180cb18c2fcbdcd2cb7bb9e724f3547c92R61. Now the error is still thrown but everything is working as expected. FYI @tpasternak
tpasternak
commented
4 months ago @ahmedyarub thank you for reporting!
ahmedyarub
commented
4 months ago Do you want me to create a PR fir this? It would be a one aliner?
ahmedyarub
commented
4 months ago
Description of the bug:
I have been manually building and testing every new commit with the latest Goland EAP and it has always worked. I have recently noticed that creating a new project fails but I'm not sure yet which commit caused that. If I enable IDE errors I can see the error in the attached log file goland.log . Note that I tested using the official build on the latest Goland release and it worked locally but not remotely. That same release was tested on a remote computer with an existing project and it worked. It seems that the bug is related to new project generation.
Which category does this issue belong to?
GoLand
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
1- Clone a Bazel project on a remote machine. 2- Import the project from scratch using Goland.
Which Intellij IDE are you using? Please provide the specific version.
Goland 2024.1 Release
What programming languages and tools are you using? Please provide specific versions.
Go
What Bazel plugin version are you using?
2024.03.26.01
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
goland.log