-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Errors in trying to use this project as a library #161
Comments
@ishanjain28 The project's original maintainer @mehrdadrad has moved on to another company (Riot Games I believe). I'm not sure how much he's planning on maintaining it going forward. I'm not entirely familiar with the project or the release process, but I'll try to give the project an org update and a new release. |
hey @tinselcity thank you for responding! I had tested this out in my own fork https://github.com/ishanjain28/vflow and just creating a new release will fix this problem. (also, I had to write my own thing for this because this project doesn't support dumping flows to ZMQ which is used by ntopng) |
Thx I put up PR: #162 Thanks so much for bringing this to our attention! |
Thanks @tinselcity! I just merged the PR and I created a new release! (v0.9.1) |
Thx so much @mehrdadrad ! |
It works fine now! thank you |
Last release was 0.9.0 back in 2020.
At that point in time, The
go.mod
in this project referred to this project as,github.com/VerizonDigital/vflow
. SeeGo tooling tries to pull the latest tag which is 0.9.0 and then fails because it's trying to download
github.com/EdgeCast/vflow
but the project in that tag is still called,github.com/VerizonDigital/vflow
.emerald :: ~/hobby/netflow.test 130 » go get -u github.com/EdgeCast/vflow/vflow go: github.com/EdgeCast/vflow@v0.9.0: parsing go.mod: module declares its path as: github.com/VerizonDigital/vflow but was required as: github.com/EdgeCast/vflow
Please create a new release. The project name in
go.mod
has been updated already so a new release should fix the problem.The text was updated successfully, but these errors were encountered: