-
Notifications
You must be signed in to change notification settings - Fork 812
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
Chore: Upgrade weaveworks/common #4462
Chore: Upgrade weaveworks/common #4462
Conversation
Signed-off-by: Arve Knudsen <[email protected]>
7d5f2c3
to
a980baa
Compare
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.
Thank you.
Please, when updating a dependency, can you list the key changes, or state that you looked and there are no key changes. |
@bboreham will do. |
@bboreham added key changes to PR description, PTAL. |
Signed-off-by: Arve Knudsen <[email protected]>
@bboreham added changelog entries, PTAL. |
Signed-off-by: Arve Knudsen <[email protected]>
Signed-off-by: Arve Knudsen <[email protected]>
@bboreham switched to using |
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.
lgtm
Yes, we can use |
* Chore: Upgrade weaveworks/common Signed-off-by: Arve Knudsen <[email protected]> * Add changelog entries Signed-off-by: Arve Knudsen <[email protected]> * Use instrument.NewHistogramCollector Signed-off-by: Arve Knudsen <[email protected]> * Use tracing.ExtractSampledTraceID Signed-off-by: Arve Knudsen <[email protected]> Signed-off-by: Alvin Lin <[email protected]>
What this PR does:
I suggest we upgrade weaveworks/common dependency to 1fa3f9fa874c.
The key changes in the new version of weaveworks/common are that
instrument.Collector.Before
andinstrument.Collector.After
now take a context argument and thatExtractTraceID
was moved to thetracing
package. Also,server.New
takes a new configuration parametercfg.GRPCListenNetwork
.I think the only change that could have any practical effect would be the switch to
cfg.GRPCListenNetwork
inserver.New
. I frankly don't know if that would affect Cortex.Which issue(s) this PR fixes:
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]