After upgrade to Goland 2026.2 getting "Build constraints exclude..." errors in editor
Setup: Goland 2026.2 running on windows, project and toolchain inside WSL (Ubuntu 24.04 LTS).
I am seeing issues like this:
Please note that for “crpyto/sha512” (also part of the SDK) not such message is shown.
My build tags are set up as follows:
Am I missing / have I overlooked some config required in Goland 2026.2?
Please sign in to leave a comment.
Some additional observation:
After multiple rounds of “Repair IDE…” and restarts, now the error is no longer about “database/sql” but about “os/signal” and “strings” (afaik both part of the SDK:
Is there anything I need to configure for e.g. the project scanning?
Same issue here (also on WSL).
Spent all morning trying to fix it by:
- deleting and re-installing go in a different path and change the GOROOT in settings
- invalidating all caches (multiple times)
In both version the GOROOT Path shows as: `\\wsl.localhost\Ubuntu\usr\local\go` in the setting menu from the wsl terminal the path `/usr/local/go/bin/go`
From the terminal everything compiles as expected. I had to downgrade to 2026.1.4 and everything works without any config changes.
Downgrading is not an option for me. I am affected by 'stat /main.go: directory not found' when running Go Build configuration on file : GO-20273, too and fix is only available in 2026.2.
Also, if possible, some minimal reproduction project would help - you can upload it here https://uploads.jetbrains.com/, and then share the upload ID with us so we could access the attachment and see if the problem comes up on our end as well.
Thank you!
Hi Vadym,
thanks for your reply. Unfortunately the problem occurs at my workplace and I am not permitted to share potentially sensitive information, so I cannot upload the requested logs.
I can give some more information, maybe that helps.
Repo size on disk is 37 MB, so I would consider it on the smaller side. It's located inside WSL FS, not on /mnt/c so FS performance should be (as) good (as possible with WSL). It consists of 9 modules and some internal packages used by those.
External dependencies (11) are vendored.
The problem can be reproduced by executing File → Invalidate caches (all options selected). I noticed during those operations that all 8 CPUs of my MS AVD are saturated (so significant other load, only Taskmanager and one Chrome instance).
In addition, I observed it's not always the build constraints issue, but sometimes methods on imported objects (e.g. sql.Tx, or errors.New()) are not properly recognized and IDE offers to implement those functions, so maybe it's indexing problem.