{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/vscode-go/issues/1121","repository_url":"https://api.github.com/repos/Microsoft/vscode-go","labels_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/1121/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/1121/comments","events_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/1121/events","html_url":"https://github.com/Microsoft/vscode-go/issues/1121","id":246413969,"number":1121,"title":"Latest version of vscode-go is vetting all vendored code","user":{"login":"tylerb","id":70804,"avatar_url":"https://avatars0.githubusercontent.com/u/70804?v=4","gravatar_id":"","url":"https://api.github.com/users/tylerb","html_url":"https://github.com/tylerb","followers_url":"https://api.github.com/users/tylerb/followers","following_url":"https://api.github.com/users/tylerb/following{/other_user}","gists_url":"https://api.github.com/users/tylerb/gists{/gist_id}","starred_url":"https://api.github.com/users/tylerb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tylerb/subscriptions","organizations_url":"https://api.github.com/users/tylerb/orgs","repos_url":"https://api.github.com/users/tylerb/repos","events_url":"https://api.github.com/users/tylerb/events{/privacy}","received_events_url":"https://api.github.com/users/tylerb/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2017-07-28T17:41:26Z","updated_at":"2017-09-18T04:54:10Z","closed_at":"2017-07-28T21:26:06Z","author_association":"CONTRIBUTOR","body":"This slows my system to a crawl. I've had to disable vet entirely.\r\n\r\nSee @ramya-rao-a comment in gitter [here](https://gitter.im/Microsoft/vscode-go?at=597b70e5bc46472974335a6b)\r\n\r\n> About vet. Long long ago we ran go tool vet filename, then that changed to go vet . to stay consistent with build and lint which operate on package rather than single file. With this we noticed that the vet flags were getting ignored. So changed that to go tool vet .. Its the go tool vet . that is picking up the vendor folders. Do log a bug for this and we can see how we can fix it\r\n\r\n\r\nI'd love to be able to run vet on just my own code."},"comment":{"url":"https://api.github.com/repos/Microsoft/vscode-go/issues/comments/330129314","html_url":"https://github.com/Microsoft/vscode-go/issues/1121#issuecomment-330129314","issue_url":"https://api.github.com/repos/Microsoft/vscode-go/issues/1121","id":330129314,"user":{"login":"dtknut","id":30921313,"avatar_url":"https://avatars2.githubusercontent.com/u/30921313?v=4","gravatar_id":"","url":"https://api.github.com/users/dtknut","html_url":"https://github.com/dtknut","followers_url":"https://api.github.com/users/dtknut/followers","following_url":"https://api.github.com/users/dtknut/following{/other_user}","gists_url":"https://api.github.com/users/dtknut/gists{/gist_id}","starred_url":"https://api.github.com/users/dtknut/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dtknut/subscriptions","organizations_url":"https://api.github.com/users/dtknut/orgs","repos_url":"https://api.github.com/users/dtknut/repos","events_url":"https://api.github.com/users/dtknut/events{/privacy}","received_events_url":"https://api.github.com/users/dtknut/received_events","type":"User","site_admin":false},"created_at":"2017-09-18T04:54:10Z","updated_at":"2017-09-18T04:54:10Z","author_association":"NONE","body":"@ramya-rao-a I am not sure there is a perfect solution.\r\n\r\nPersonally, I had vetOnSave set to ```package```, but was editing a main.go file in the root folder. For this case one could maybe run ```go tool vet main.go``` to avoid picking up the vendor folder. I am not sure if this would cause any other issues. It is not exactly doing what ```package``` implies."}}
{"actor":{"display_login":"dtknut"}}