Skip to content
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

HPCC-31683 Highlight metrics with outlier values #18867

Merged

Conversation

GordonSmith
Copy link
Member

@GordonSmith GordonSmith commented Jul 10, 2024

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@GordonSmith GordonSmith requested a review from jeclrsg July 10, 2024 14:34
Copy link

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-31683

Jirabot Action Result:
Updated PR

@GordonSmith GordonSmith force-pushed the HPCC-31683-SKEW_COLOR branch 3 times, most recently from 97aa397 to 7c051ed Compare July 11, 2024 11:13
@GordonSmith
Copy link
Member Author

Rebased and fixed conflicts for pull

@GordonSmith GordonSmith force-pushed the HPCC-31683-SKEW_COLOR branch from 7c051ed to e9bf087 Compare July 11, 2024 11:22
@GordonSmith GordonSmith requested a review from jeclrsg July 11, 2024 13:46
@GordonSmith GordonSmith merged commit 54db65d into hpcc-systems:candidate-9.2.x Jul 11, 2024
50 of 51 checks passed
@GordonSmith GordonSmith deleted the HPCC-31683-SKEW_COLOR branch July 11, 2024 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants