What version of Go, VS Code & VS Code Go extension are you using?

Share the Go related settings you have added/edited

Run Preferences: Open Settings (JSON) command to open your settings.json file.
Share all the settings with the go. or ["go"] or gopls prefixes.

{
    "go.toolsManagement.autoUpdate": true,
    "go.lintTool": "golint",
    "go.vetOnSave": "workspace"
}

Describe the bug

When "Go:vet On Save is enabled in settings; and a go file is edited and saved (containing an error that go vet ./... does pick up), then no error squiggles appear in the editor to show that there is a vet error.

Required behavior

When "Go:vet On Save is enabled in settings; and a go file is edited and saved (containing an error that go vet ./... does pick up), then error squiggles MUST appear in the editor to show that there is a vet error.

Steps to reproduce the behavior:

1. given a go file testvet.go with the following code

package testvet

import (
	"fmt"
	"sync"
)

// TestThatVetRunsOnSave minimal code to show vet not running on save in VS code
func TestThatVetRunsOnSave() {

	ch := make(chan string)
	var wg sync.WaitGroup
	wg.Add(1)
	go printit(wg, ch)

	ch <- "one"
	ch <- "two"
	close(ch)
	wg.Wait()
	fmt.Println("done.")

}

func printit(wg sync.WaitGroup, ch chan string) {
	defer wg.Done()
	for t := range ch {
		fmt.Println(t)
	}
}

2. When I edit any text in this file that changes something, for example a space or comment
3. Then the editor should highlight the same lines of code containing vet errors, that the command line go vet ./... picks up as having an error.

pkg/testvet/testvet.go:14:13: call of printit copies lock value: sync.WaitGroup contains sync.noCopy
pkg/testvet/testvet.go:24:17: printit passes lock by value: sync.WaitGroup contains sync.noCopy

4. Manually running the command , Go:vet workspace does work and causes the editor to report the correct errors and squigglies. (see screenshot below)

Screenshots or recordings

To be clear, the screenshot below is the behaviour that we WANT to happen and be triggered on save, this is currently not happening and only happens when you manually run the command Go;vet workspace

In addition to this functionality not working, the user interface helptext in VSCode settings does not make sense. The setting helptext has this text, which refers to functionality that I believe is not longer valid.

I have tried all variations of this setting value; both package and workspace. Neither works.