Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

golint error for one of the method in etcdops.go #1676

Closed
shuklanirdesh82 opened this issue Aug 2, 2017 · 4 comments
Closed

golint error for one of the method in etcdops.go #1676

shuklanirdesh82 opened this issue Aug 2, 2017 · 4 comments

Comments

@shuklanirdesh82
Copy link
Contributor

shuklanirdesh82 commented Aug 2, 2017

#1661 introduces following, make build is also complaining about the same.

$ make -s build
drivers/shared/etcdops.go:89:39: exported func NewKvStore returns unexported type *shared.etcdKVS, which can be annoying to use

/CC @tusharnt

@luomiao
Copy link
Contributor

luomiao commented Aug 2, 2017

oops. thanks for catching this.
It's strange that I didn't see this error in either local or CI testing...
Is it a warning or error?

@luomiao
Copy link
Contributor

luomiao commented Aug 2, 2017

I found the CI testing of this PR:
https://ci.vmware.run/vmware/docker-volume-vsphere/1384

CI returns success while in the beginning it gave this warning:

$ make -s build
drivers/shared/etcdops.go:89:39: exported func NewKvStore returns unexported type *shared.etcdKVS, which can be annoying to use
warning: no packages being tested depend on github.com/vmware/docker-volume-vsphere/client_plugin/drivers/shared
warning: no packages being tested depend on github.com/vmware/docker-volume-vsphere/client_plugin/shared_plugin

Is it possible to fail CI if there is a warning?

And regarding to this warning, it will be gone when we finish the refactoring of the shared plugin.

@shuklanirdesh82
Copy link
Contributor Author

Hey @luomiao, our build script is not strict for golint or pylint warnings/errors due to time constraints and we have an issue open to make python code to compliant with pylint warning. Post vmworld it is possible to restrict the build incase of such warning till then we have to look manually while proposing the new code change.

It will be great if you can supply a quick fix or include any of your ongoing PR to turn off such warning. Since #1661 merged all our builds are having such warning.

@luomiao
Copy link
Contributor

luomiao commented Aug 9, 2017

Resolved in #1687

@luomiao luomiao closed this as completed Aug 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants