-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Support tracer env based initialization in hotrod #1115
Support tracer env based initialization in hotrod #1115
Conversation
Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
18be51c
to
9ba407b
Compare
Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
07a2cb0
to
87116e9
Compare
Looks like the build error is caused by change in glide.lock |
@@ -233,7 +233,7 @@ imports: | |||
- name: github.com/uber-go/atomic | |||
version: 8474b86a5a6f79c443ce4b2992817ff32cf208b8 | |||
- name: github.com/uber/jaeger-client-go | |||
version: b043381d944715b469fd6b37addfd30145ca1758 | |||
version: 1a782e2da844727691fef1757c72eb190c2909f0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you update the verson in glide.yml?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I did, but still error from ingester.
This reverts commit 04a4652. Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
18bad7a
to
aa7edfb
Compare
readme needs to be updated too |
glide update will probably update other deps too. But you didn't add go client bump in glide.yml |
@pavolloffay |
Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
it's tagged during the release process - tag on github. Not need to tag it/change the version explicitly. |
Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
34c0f68
to
620fd7d
Compare
examples/hotrod/README.md
Outdated
@@ -49,10 +49,11 @@ go run ./main.go all | |||
docker run \ | |||
--rm \ | |||
--link jaeger \ | |||
--env JAEGER_AGENT_HOST=jaeger \ | |||
--env JAEGER_AGENT_PORT=6831 \ | |||
-p8080-8083:8080-8083 \ | |||
jaegertracing/example-hotrod:1.6 \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.6 version is old, so it needs to be updated to accept JAEGER_AGENT_XXX env.
Should I remove version tag so that latest is pulled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has to be updated. latest is fine or 1.8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to latest
Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
let's pin sarama and sarama-cluster to 1.16.0 and 2.1.13 respectively, looks like there was a breaking change. |
More specifically https://github.com/bsm/sarama-cluster/blame/f7d869db45fd8d74bf62c02a9d17637f945668d0/partitions.go#L23 was added to the interface in the newest version of sarama-cluster |
Signed-off-by: Eundoo Song <eundoo.song@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #1115 +/- ##
======================================
Coverage 100% 100%
======================================
Files 142 142
Lines 6743 6743
======================================
Hits 6743 6743 Continue to review full report at Codecov.
|
Pin sarama and sarama-cluster to 1.16.0 and 2.1.13 is done. |
@eundoosong thanks! |
Which problem is this PR solving?
Short description of the changes