You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users of IDEs such as VSCode may want to use a rules_go sdk for tooling, so that the tools use the same go as the code. This path should be stable across versions of rules_go. In bzlmod rules_go, this regressed.
What version of rules_go are you using?
0.46.0
What version of gazelle are you using?
0.35.0
What version of Bazel are you using?
7.0.2
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
macOS / arm
Any other potentially useful information about your toolchain?
Using bzlmod, VSCode
What did you do?
Update to bzlmod rules go while using vscode
What did you expect to see?
No IDE errors relating to ${workspaceFolder}/bazel-${workspaceFolderBasename}/external/go_sdk
What did you see instead?
${workspaceFolder}/bazel-${workspaceFolderBasename}/external/go_sdk is missing.
It can be replaced as a workaround by a long path that includes some cruft and the rules_go version, i.e. ${workspaceFolder}/bazel-${workspaceFolderBasename}/external/rules_go0.46.0go_sdk~main___download_0
The text was updated successfully, but these errors were encountered:
Users of IDEs such as VSCode may want to use a
rules_go
sdk for tooling, so that the tools use the same go as the code. This path should be stable across versions ofrules_go
. In bzlmodrules_go
, this regressed.What version of rules_go are you using?
0.46.0
What version of gazelle are you using?
0.35.0
What version of Bazel are you using?
7.0.2
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
macOS / arm
Any other potentially useful information about your toolchain?
Using bzlmod, VSCode
What did you do?
Update to bzlmod rules go while using vscode
What did you expect to see?
No IDE errors relating to ${workspaceFolder}/bazel-${workspaceFolderBasename}/external/go_sdk
What did you see instead?
${workspaceFolder}/bazel-${workspaceFolderBasename}/external/go_sdk is missing.
It can be replaced as a workaround by a long path that includes some cruft and the rules_go version, i.e. ${workspaceFolder}/bazel-${workspaceFolderBasename}/external/rules_go
0.46.0go_sdk~main___download_0The text was updated successfully, but these errors were encountered: