-
## Information
**VIM version**
NVIM v0.2.2
Build type: Release
LuaJIT 2.0.5
Operating System: WHAT OS WERE YOU USING?
macOS 10.13.3
### :ALEInfo
```
Current Filetype: go
Ava…
-
We now have gometalinter enabled on travis:
https://github.com/google/syzkaller/blob/master/.gometalinter.json
However, not all checkers are enabled and some errors are suppressed. We should gradual…
-
### Description
As described in #1287, we'd like to run gometalinter in CI. We need to identify which checks we can run automatically that won't generate false positives. We'll list these checks he…
-
Can be worthwhile.
It's interesting to see exact CI run time difference with it.
Although I think our pipeline is bottlenecked with installation of packages rather than linting.
Anyway, if our fi…
-
I've been using this package for a few weeks, and have noticed the following message pop up periodically. The package works most of the time, but seems to have some weird interaction with the `plugin_…
-
Hi!
Some users of my client are looking to use alternate linters for diagnostics, specifically [golangci/golangci-lint](https://github.com/golangci/golangci-lint). Could multiple linters be supported…
-
I've been using VSCode on this project for a few months. VSCode and this plugin have been working fine right along, very few problems.
With the installation of the July 2018 release of VSCode, sudd…
-
**Describe the bug**
CreateVolume and NodePublishVolume have a high complexity according to gocyclo. They should be simplified.
**Steps to reproduce**
Steps to reproduce the behavior:
1. Run `…
-
```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x10c3a5d]
goroutine 1 [running]:
main.(*branchStack).ge…
-
The goreleaser configuration does not include the new `gochecknoinits` and `gochecknoglobals` linters.
I used goreleaser to build the master branch and after putting the contents of the resulting …
thsnr updated
6 years ago