Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-compilation issue with input zipkin plugin #3100

Closed
Alessar opened this issue Aug 8, 2017 · 7 comments
Closed

Non-compilation issue with input zipkin plugin #3100

Alessar opened this issue Aug 8, 2017 · 7 comments
Labels
upstream bug or issues that rely on dependency fixes

Comments

@Alessar
Copy link

Alessar commented Aug 8, 2017

There are several non-compilation errors in master branch:

../../plugins/inputs/zipkin/handler.go:12:2: cannot find package "github.com/openzipkin/zipkin-go-opentracing/_thrift/gen-go/zipkincore"

Related with openzipkin-contrib/zipkin-go-opentracing@a3dd956
And with 137b312

@danielnelson
Copy link
Contributor

Not that I'm against it, it seems like it would be good to be on the latest tag, but is there any particular reason you want to upgrade zipkin-go-opentracing library?

cc @goller

@danielnelson
Copy link
Contributor

@Alessar I'm closing because I don't know the reason behind the issue, if you can provide more information then please reopen.

@Alessar
Copy link
Author

Alessar commented Aug 18, 2017

Default go get behaviour is to download latest sources, so it is good that telegraf will use latest version of another libraries (I hope that another libraries will have the stable HEAD always).

@danielnelson
Copy link
Contributor

Can you add the full command you are running to produce the error?

@Alessar
Copy link
Author

Alessar commented Sep 14, 2017

go get github.com/influxdata/telegraf
cd $GOPATH/src/github.com/influxdata/telegraf/cmd/telegraf
go get

@danielnelson
Copy link
Contributor

Thanks, I will get this fixed. I recommend using the targets in the Makefile though in general since getting the HEAD of each dependency is bound to cause lots of problems.

@danielnelson danielnelson reopened this Sep 14, 2017
@danielnelson
Copy link
Contributor

After updating to the lastest zipkin-go-opentracing release version I get:

# github.com/openzipkin/zipkin-go-opentracing/thrift/gen-go/scribe
../../openzipkin/zipkin-go-opentracing/thrift/gen-go/scribe/scribe.go:333: cannot use scribeProcessorLog literal (type *scribeProcessorLog) as type thrift.TProcessorFunction in assignment:
        *scribeProcessorLog does not implement thrift.TProcessorFunction (wrong type for Process method)
                have Process(context.Context, int32, thrift.TProtocol, thrift.TProtocol) (bool, thrift.TException)
                want Process(int32, thrift.TProtocol, thrift.TProtocol) (bool, thrift.TException)
../../openzipkin/zipkin-go-opentracing/thrift/gen-go/scribe/scribe.go:341: too many arguments in call to processor.Process
        have (context.Context, int32, thrift.TProtocol, thrift.TProtocol)
        want (int32, thrift.TProtocol, thrift.TProtocol)

I believe we need to wait for github.com/apache/thrift to release 0.11 in order to fix this issue, according to openzipkin-contrib/zipkin-go-opentracing#68

@danielnelson danielnelson added the upstream bug or issues that rely on dependency fixes label Sep 26, 2017
@Alessar Alessar closed this as completed Jul 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream bug or issues that rely on dependency fixes
Projects
None yet
Development

No branches or pull requests

2 participants