-
Notifications
You must be signed in to change notification settings - Fork 2
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
Unable to build Lagrande due to missing dependency #3
Comments
Thanks for reporting! It got removed as I was cleaning stuff up so I'll change the dependency. |
Ok, right. I figured it out. I think I can PR for this sometime by lunchtime tomorrow. 🤞 Thanks for the comments in the code! 🙏 |
The timescale publisher is not on the upstream (influxdata/telegraf). If you are not looking to test Timescale, you can remove that part of the code for your local build. Otherwise I'll have to see if I have that on a backup somewhere (or just rewrite it, that might actually be faster 😅) |
Yeah, there's something I don't get about @svenklemm 's fork. He also requires You can see what I got wired up so far here. I'll give it another go tomorrow. 😛 |
Until aleveille#3 is fixed, this code can't be built.
For what it's worth, I've re-forked the Telegraf repo. The build is now passing on my machine, so this might be enough to get the build working on your machine, but I haven't run any test yet to ensure if the application is still OK. |
So, I tried building with the fork from Docker from Go versions 1.9 to 1.15 and am consistently unable to either for n in {9..15}; do
podman run --rm -it "registry.hub.docker.com/library/golang:1.${n}-alpine" /bin/sh -c "apk add -U git &> /dev/null && go get -v github.com/aleveille/lagrande && echo 'it works' || echo 'it does not work'"
done It fails with:
I get the same results when building locally. Likewise if I initialize it with
There's something I'm still missing here... |
It seems a dependency is declared to
aleveille/telegraf
inpublisher/timescalePublisher.go
, but that repository is either non-existent or private.The text was updated successfully, but these errors were encountered: