-
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
[receiver/riak] Riak Metric Receiver #8548
Conversation
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.
Overall looks quite good. A few things need another look though.
We also need to add an integration test like this one.
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.
Please add this module to the CODEOWNERS file with the two of us listed as owners.
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.
Please add the component to the root go.mod
(include a replace
directive) and also cmd/configschema
tests.
@armstrmi CI is still failing on this:
|
|
👍 The integration test is running successfully:
|
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. Thanks @armstrmi!
I'm waiting on the new release to be performed before merging this. It would probably cause this PR to get outdated (like, the changelog and go.mod/sum). |
I appreciate the thumbs up from the contributors but I definitely wish that maintainers instead took the effort to update existing PRs when they make changes that break them, including releases. |
I agree with you, @anuraaga. I think most of us are trying that, but there are cases where it's not possible/feasible. In this case, the release hasn't been made and I was about to leave for the day, but wanted to make it clear (also to other maintainers) that this wouldn't get merged before the release. |
Cool sounds like the sentiment is there. |
Forgot another case where we can't do it (which is the case with this PR as well): if contributors don't mark the PR as "maintainers can change it", we can't add commits or force push a change to the PR. The best we can then do is push the branch to our own forks, and offer it to the contributor. |
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.
As @djaglowski noticed, changelog needs to be cleaned up from the duplicate entries
@djaglowski @jpkrohling do we have an issue for this? Update: Saw the issue in the description. don't know how you folks can carefully review 5500 lines in a reasonable amount of time :)) probably you spent lots of time... |
@bogdandrutu yes we do, #8364 |
It can easily be done in an unreasonable amount of time :) More seriously, my strategy has been to approach it as multiple review sessions. Start with obvious issues / gaps. Then focus on config and data model. Then factory and scraper. Double check tests and coverage. Finally checking all minor details. |
Necessary changes to address feedback were simple and clear and have been completed.
Description: Adding New Component: Riak Metric Receiver,
Link to tracking Issue: New Component: Riak Metric Receiver
Testing: series of testing was added including
As well as sample configs for running local riak receiver and verify that metrics are being received
Documentation: README.md