[release] prepare v0.28.0 release

c0e33de src/goEnvironmentStatus: update hard coded go versions
81f6db9 src/goModules: update example module names to reflect naming guidelines
ba2daa3 src/goMain.ts: disable check for active debug session
d32a326 package.json: drop minify when packaging
cc6f312 src/debugAdapter: let infer path logic handle non-existing files
5a59bbf src/goDebugConfiguration: remote attach should not be warned about port
1d258a2 src/goTest: group test explorer settings, fix bugs
104052d package.json: update gopls settings (v0.7.2)
dc044d1 test/integration: write legacy DA trace line-by-line
3a09d5d test/integration: log DAP trace when legacy adapter test fails
9248382 src/config: remove WrappedConfiguration in favor of trusted workspace
fb6208d docs: change blog.golang.org to go.dev/blog
ab3d3a6 src/goDebugFactory: add --check-go-version=false
9a9ec9a src/goTest: cleanup
b9bf001 src/goTest: basic profiling support
850fefd test/integration/goTest: remove unused imports
d1d9901 src/goTest: fix test run cancellation
977e93e docs/debugging.md: add FAQ section for next while nexting
6019957 src/goTest: support running sub-tests
9021bff src/goTest: do not set range for dynamic subtests
1c36262 src/goDebugConfiguration: show warning that port is being used
09d4bbe docs/debugging.md: update description of port and host
41279a6 Revert "src/goDebugFactory.ts: direct users to use 'debugServer' for remote"
a4c2c4a CHANGELOG.md: prep for v0.27.2
53accf5 src/goDebugFactory: fix debugger launch on Windows
e6c2d3c all: change learn.go.dev to go.dev/learn
aa3293c src/goDebugConfiguration: massage launch config for debug/test
289839c test/integration/goDebug.test.ts: enable disconnect tests
c069def src/goTest: remove unused names
e53d60e src/goTest: clean up test ID parsing
3e12e73 src/goTest: split up test explorer
a1cc5e5 src/goInstallTools: unpin dlv-dap version, and pick master
2ff7ead src/goTestExplorer: handle stretchr suites
33d814a .github: update issue template to collapse version details
ebd07b1 src/goDebugConfiguration+docs: improve dlvLoadConfig communication
c3de634 codelens: fix regexps for test funcs names
2f484bd src/goTestExplorer: handle weird doc URIs on load
c79e0c4 src/goDebugFactory: increase timeout for dlv dap server start
3f434bd all: bundle with esbuild instead of webpack
83aa2cb src/goTestExplorer: implement a test provider for the new test api
945a47e package.json: recognize *.*tmpl as go template files
ad3a6ca all: add support for go.work files as go.mod files
0ff533d tools/relnotes: use types from work-stats package
e81d5fc CHANGELOG.md: v0.27.1 change log
46b3efe src/goToolsInformation: use the commit hash to pin dlv-dap version
e0a268b package-lock.json: npm audit fix
336b9f7 src/goDebugConfiguration: convert processId to int
b4226ab package.json: add support for replay and core debug modes
6060589 docs/debugging.md: add FAQ section
6a6fdb6 src/goDebugFactory: log errors without killing delve process
4e7f6f5 src/goMain: export a small API
8a4731f package.json: start v0.28.0-dev
cd72252 package.json: use fileDirname for Launch Package snippet
f77de39 CHANGELOG.md: mention the removal of 'port' support in dlv-dap
45b06e0 src/goDebugFactory.ts: direct users to use 'debugServer' for remote

Updates #1776

Change-Id: Ifd897cf869e1f1a485026d0631b88b00d2ec83ce

Author: hyangah

.github/ISSUE_TEMPLATE/bug_report.md

@@ -6,7 +6,7 @@ labels: ''
 assignees: ''
 
 ---
-
+<!--
 For asking questions, see:
 - [Stack Overflow](https://stackoverflow.com/questions/tagged/go+visual-studio-code)
 - [GitHub Discussions (Help)](https://github.com/golang/vscode-go/discussions/categories/help)
@@ -17,8 +17,11 @@ Before filing an issue, please review our troubleshooting guides
 * [Troubleshooting other problems](https://github.com/golang/vscode-go/tree/master/docs/troubleshooting.md)
 
 Please answer these questions before submitting your issue. Thanks!
+-->
 
 ### What version of Go, VS Code & VS Code Go extension are you using?
+<details><summary>Version Information</summary><br>
+
 * Run `go version` to get version of Go from _the VS Code integrated terminal_.
 	- <Paste go version here>
 * Run `gopls -v version` to get version of Gopls from _the VS Code integrated terminal_.
@@ -29,6 +32,7 @@ Please answer these questions before submitting your issue. Thanks!
 	- <Paste Go extension version here>
 * Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > `Go: Locate Configured Go Tools` command.
 	- <Paste the output here>
+</details>
 
 ### Share the Go related settings you have added/edited
 

.vscode/extensions.json

@@ -0,0 +1,3 @@
+{
+	"recommendations": ["connor4312.esbuild-problem-matchers"]
+}

.vscode/launch.json

@@ -25,7 +25,7 @@
 			"stopOnEntry": false,
 			"sourceMaps": true,
 			"smartStep": true,
-			"preLaunchTask": "npm: webpack",
+			"preLaunchTask": "npm: bundle-dev",
 			"env": {
 				"VSCODE_GO_IN_TEST": ""  // Enable code
 			},
@@ -44,7 +44,7 @@
 			],
 			"sourceMaps": true,
 			"smartStep": true,
-			"preLaunchTask": "npm: webpack"
+			"preLaunchTask": "npm: bundle-dev"
 		},
 		{
 			"name": "Launch Extension Tests",
@@ -61,7 +61,8 @@
 				"999999"
 			],
 			"env": {
-				"VSCODE_GO_IN_TEST": "1"  // Disable code that shouldn't be used in test
+				"VSCODE_GO_IN_TEST": "1",  // Disable code that shouldn't be used in test
+				"MOCHA_TIMEOUT": "999999",
 			},
 			"stopOnEntry": false,
 			"sourceMaps": true,

.vscode/tasks.json

@@ -50,6 +50,22 @@
 				"kind": "build",
 				"isDefault": true
 			}
+		},
+		{
+			"type": "npm",
+			"script": "bundle-watch",
+			"group": "build",
+			"problemMatcher": "$esbuild-watch",
+			"isBackground": true,
+			"presentation": {
+				"reveal": "never"
+			}
+		},
+		{
+			"type": "npm",
+			"script": "bundle-dev",
+			"group": "build",
+			"problemMatcher": "$esbuild",
 		}
 	]
 }

.vscodeignore

@@ -18,4 +18,3 @@ third_party/
 tools/
 tsconfig.json
 typings/
-webpack.config.js

docs/commands.md

@@ -59,6 +59,18 @@ Runs all unit tests in the current file.
 
 Runs all unit tests in the package of the current file.
 
+### `Go Test: Refresh`
+
+Refresh a test in the test explorer. Only available as a context menu option in the test explorer.
+
+### `Go Test: Show Last Profile`
+
+Show last captured profile
+
+### `Go Test: Profile`
+
+Run a test and capture a profile
+
 ### `Go: Benchmark Package`
 
 Runs all benchmarks in the package of the current file.

docs/debugging.md

@@ -246,12 +246,12 @@ Here is the list of attributes specific to Go debugging.
 | `dlvFlags` | Extra flags for `dlv`. See `dlv help` for the full list of supported. Flags such as `--log-output`, `--log`, `--log-dest`, `--api-version`, `--output`, `--backend` already have corresponding properties in the debug configuration, and flags such as `--listen` and `--headless` are used internally. If they are specified in `dlvFlags`, they may be ignored or cause an error.<br/> | <center>_same as Launch_</center>|
 | `env` | Environment variables passed to the program.<br/> | <center>_n/a_</center> |
 | `envFile` | Absolute path to a file containing environment variable definitions. Multiple files can be specified by provided an array of absolute paths<br/>(Default: `${workspaceFolder}/.env`)<br/> | <center>_n/a_</center> |
-| `host` | The host name of the machine the delve debugger will be listening on.<br/>(Default: `"127.0.0.1"`)<br/> | <center>_same as Launch_</center>|
+| `host` | In legacy mode, this will only apply to remote-attach configurations, which will look for "dlv ... --headless --listen=<host>:<port>" server started externally. In dlv-dap mode (which does not yet support remote-attach), this will apply to all other configurations. The extension will try to connect to an external server started with "dlv dap --listen=<host>:<port>" to ask it to launch/attach to the target process.<br/>(Default: `"127.0.0.1"`)<br/> | <center>_same as Launch_</center>|
 | `logDest` | dlv's `--log-dest` flag. See `dlv log` for details. Number argument is not allowed. Supported only in `dlv-dap` mode, and on Linux and Mac OS.<br/> | dlv's `--log-dest` flag. See `dlv log` for details. Number argument is not allowed. Supported only in `dlv-dap` mode and on Linux and Mac OS.<br/> |
 | `logOutput` | Comma separated list of components that should produce debug output. Maps to dlv's `--log-output` flag. Check `dlv log` for details.<br/><p>Allowed Values: `"debugger"`, `"gdbwire"`, `"lldbout"`, `"debuglineerr"`, `"rpc"`, `"dap"`<br/>(Default: `"debugger"`)<br/> | <center>_same as Launch_</center>|
 | `mode` | One of `auto`, `debug`, `test`, `exec`, `replay`, `core`. In `auto` mode, the extension will choose either `debug` or `test` depending on active editor window.<br/><p>Allowed Values: `"auto"`, `"debug"`, `"test"`, `"exec"`, `"replay"`, `"core"`<br/>(Default: `auto`)<br/> | Indicates local or remote debugging. Local maps to the `dlv attach` command, remote maps to `connect`. `remote` is not supported in `dlv-dap` mode currently. Use `host` and `port` instead.<br/><p>Allowed Values: `"local"`, `"remote"`<br/>(Default: `local`)<br/> |
 | `output` | Output path for the binary of the debugee.<br/>(Default: `"debug"`)<br/> | <center>_n/a_</center> |
-| `port` | The port that the delve debugger will be listening on.<br/>(Default: `2345`)<br/> | <center>_same as Launch_</center>|
+| `port` | In legacy mode, this will only apply to remote-attach configurations, which will look for "dlv ... --headless --listen=<host>:<port>" server started externally. In dlv-dap mode (which does not yet support remote-attach), this will apply to all other configurations. The extension will try to connect to an external server started with "dlv dap --listen=<host>:<port>" to ask it to launch/attach to the target process.<br/>(Default: `2345`)<br/> | <center>_same as Launch_</center>|
 | `processId` | <center>_n/a_</center> | <br/><p><b>Option 1:</b> Use process picker to select a process to attach, or Process ID as integer.<br/><p>Allowed Values: `"${command:pickProcess}"`, `"${command:pickGoProcess}"`<br/><br/><p><b>Option 2:</b> Attach to a process by name. If more than one process matches the name, use the process picker to select a process.<br/><br/><p><b>Option 3:</b> The numeric ID of the process to be debugged. If 0, use the process picker to select a process.<br/><br/>(Default: `0`)<br/> |
 | `program` | Path to the program folder (or any go file within that folder) when in `debug` or `test` mode, and to the pre-built binary file to debug in `exec` mode. If it is not an absolute path, the extension interpretes it as a workspace relative path.<br/>(Default: `"${workspaceFolder}"`)<br/> | <center>_n/a_</center> |
 | `remotePath` | <center>_n/a_</center> | (Deprecated) *Use `substitutePath` instead.*<br/>The path to the source code on the remote machine, when the remote path is different from the local machine. If specified, becomes the first entry in substitutePath.<br/>(Default: `""`)<br/> |
@@ -441,6 +441,22 @@ The legacy adapter used `dlvLoadConfig` as one-time session-wide setting to over
 
 Please [open an issue](https://github.com/golang/vscode-go/issues/new) if this is not sufficient for your use case or if you have any additional feedback.
 
+### Why does my debug session have an `invalid command` error when I try to step?
+
+When stepping through a program on a particular goroutine, the debugger will make sure that the step is completed, even when interrupted by events on a different goroutine. If a breakpoint is hit on a different goroutine, the debug adapter will stop the program execution to allow you to inspect the state, even though the step request is still active.
+
+If you attempt to make another step request you will get an `invalid command` error.
+
+<p align="center"><img src="images/invalidCommandExceptionInfo.png" alt="Disable breakpoints from the Breakpoints context menu" width="75%"> </p>
+
+
+Use `Continue` to resume program execution.
+
+If you do not want the step request to be interrupted, you can disable all breakpoints from VS Code from the context menu in the `Breakpoints` view.
+
+<p align="center"><img src="images/disablebps.png" alt="Disable breakpoints from the Breakpoints context menu" width="75%"> </p>
+
+
 [Delve]: https://github.com/go-delve/delve
 [VS Code variables]: https://code.visualstudio.com/docs/editor/variables-reference
 [snippets]: https://code.visualstudio.com/docs/editor/userdefinedsnippets

docs/gopath.md

@@ -8,7 +8,7 @@ directories. Your code is typically located in the `$GOPATH/src` directory.
 If you are not familiar with Go and `GOPATH`, please first read about [writing
 Go code with `GOPATH`](https://golang.org/doc/gopath_code.html#GOPATH).
 
-**If you are just starting out with Go, we recommend [using Go modules](https://blog.golang.org/using-go-modules) instead of GOPATH.**
+**If you are just starting out with Go, we recommend [using Go modules](https://go.dev/blog/using-go-modules) instead of GOPATH.**
 
 ## Overview
 
@@ -82,4 +82,4 @@ This can be done by setting [`"go.toolsGopath"`](settings.md#go.toolsGopath) to
 
 The extension will fall back to your existing `GOPATH` if tools are not found in the [`go.toolsGopath`](settings.md#go.toolsGopath) directory.
 
-[Go modules]: https://blog.golang.org/using-go-modules
+[Go modules]: https://go.dev/blog/using-go-modules