-
Notifications
You must be signed in to change notification settings - Fork 9.1k
[HDDS-1201] Reporting corrupted containers info to SCM #1032
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
Conversation
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
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, LGTM
This patch introduced new checkstyle errors. I recommend to add ozone label to the jira to get clear reports from the supplementary jenkins instance. Contributors (who has no write access to the repository) can add ozone label with a new comment with the "/label ozone" message. |
@elek sorry about that. I have filed HDDS-1794 to fix this. |
Oh, no worries at all. It's a problem with the build system if these minor problems are not clearly visible immediately on the PR. I just tried to share how can it be avoid, but I am also thinking to document it better on the wiki. (ps: I am also experimenting with helper scripts such as |
SAMZA-2193: Fix unit-test failure after making rate limiter as a required config
The previous patch for this jira did not implement the logic completely. Also there was no integration test to verify end-to-end functionality. Both these issues have been fixed as part of this change.