-
Notifications
You must be signed in to change notification settings - Fork 111
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
NR Control Health Checks #1250
NR Control Health Checks #1250
Conversation
🦙 MegaLinter status: ❌ ERROR
See detailed report in MegaLinter reports |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## super-agent #1250 +/- ##
==============================================
Coverage ? 81.22%
==============================================
Files ? 202
Lines ? 22352
Branches ? 3545
==============================================
Hits ? 18155
Misses ? 3020
Partials ? 1177 ☔ View full report in Codecov by Sentry. |
47cc4ae
to
30f3771
Compare
c93dfa4
to
d1ef5c2
Compare
df4a0e6
to
6eb724b
Compare
d1ef5c2
to
73f27aa
Compare
aad0176
to
4b95e2f
Compare
There were way too many string comparisons and hard coded strings going on in the super agent health file, so I've refactored it somewhat. I'm looking for it to use integers in every conceivable spot to minimize string comparisons and copies, as well as reduce the risk of a future change introducing bugs because we're comparing status messages that are hard coded in 2 places, rather than using integer codes. To that end, I've redone the file to use the original integer codes as the enum values, eliminated all cases where we have a string like I also removed the large block of logic to construct different status messages and modeled it somewhat after the logic used in |
4b95e2f
to
3ac48d5
Compare
73f27aa
to
5e48f62
Compare
Co-authored-by: Timothy Pansino <[email protected]>
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.
Looks good!
Before contributing, please read our contributing guidelines and code of conduct.
Overview
Describe the changes present in the pull request
Related Github Issue
Include a link to the related GitHub issue, if applicable
Testing
The agent includes a suite of tests which should be used to
verify your changes don't break existing functionality. These tests will run with
Github Actions when a pull request is made. More details on running the tests locally can be found
here,
For most contributions it is strongly recommended to add additional tests which
exercise your changes.