vscode-go
vscode-go copied to clipboard
golang
vscode-go: add option to disable tool recompilation prompts
Outdated tool detection relies on go version -m, i.e. it does not work in many institutional settings. Shell scripts with alternative tools, shim scripts, or something like dotslash will all lead to a spurious warning in the IDE to recompile tools.
This PR adds a configuration option, go.toolsManagement.warnOutdated, that can be set to disable the notification if you know better.
Default behaviour should be unchanged.
Updates https://github.com/golang/vscode-go/issues/3637.
This PR (HEAD: bb2b143c9ad5a0e2cd4cf7fca0aeb8677a45d134) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/vscode-go/+/659815.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to log in to Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Gopher Robot:
Patch Set 1:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Gopher Robot:
Patch Set 1:
Congratulations on opening your first change. Thank you for your contribution!
Next steps: A maintainer will review your change and provide feedback. See https://go.dev/doc/contribute#review for more info and tips to get your patch through code review.
Most changes in the Go project go through a few rounds of revision. This can be surprising to people new to the project. The careful, iterative review process is our way of helping mentor contributors and ensuring that their contributions have a lasting impact.
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
This PR (HEAD: b92b631791468aa83e38341b8a6296d528492f3c) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/vscode-go/+/659815.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to log in to Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Hongxiang Jiang:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Ethan Reesor:
Patch Set 2: Commit-Queue+1
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 2:
Dry run: CV is trying the patch.
Bot data: {"action":"start","triggered_at":"2025-03-21T17:39:22Z","revision":"0e1d73305b93cd73263fa27034d1af43236387d9"}
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from kokoro:
Patch Set 2:
Kokoro presubmit build queued for golang/vscode-go/gcp_ubuntu/presubmit Logs at: http://sponge2.corp.google.com/16cb05d0-be72-448b-a6b3-f957857c9868
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from kokoro:
Patch Set 2:
Kokoro presubmit build starting for golang/vscode-go/gcp_ubuntu/presubmit Logs at: https://source.cloud.google.com/results/invocations/16cb05d0-be72-448b-a6b3-f957857c9868
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Ethan Reesor:
Patch Set 2: -Commit-Queue
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 2:
This CL has failed the run. Reason:
Tryjob golang/try/x_vscode-go-gotip-linux-amd64_docker has failed with summary (view all results):
- go on master (commit c0392e7)
- vscode-go on master (change 659815)
Build or test failure, click here for results.
To reproduce, try gomote repro 8719767433837899441.
Additional links for debugging:
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 2: LUCI-TryBot-Result-1
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from kokoro:
Patch Set 2: kokoro-CI-1
Kokoro presubmit build finished with status: FAILURE Logs at: https://source.cloud.google.com/results/invocations/16cb05d0-be72-448b-a6b3-f957857c9868
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Hongxiang Jiang:
Patch Set 2:
(2 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Ethan Reesor:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Hongxiang Jiang:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from thumphries:
Patch Set 2:
(2 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Hongxiang Jiang:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Ethan Reesor:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from thumphries:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!
Message from Ethan Reesor:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/659815. After addressing review feedback, remember to publish your drafts!