Skip to content

Conversation

@theyostalservice
Copy link
Contributor

Description

We had an internal report for this issue. For percentile measures, there's an additional group of arguments that must be changed to fit the new YAML format when converting them to metrics, and we were not doing that.

The included tests should show the appropriate behaviors when converting the measure. In addition, I manually tested the new exception case by setting both use_discrete_percentile and use_approximate_percentile to true in a measure and running the script, and I saw the following error:
Screenshot 2026-01-18 at 1 33 39 PM

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Checklist

  • Ran uv tool run ruff format --config pyproject.toml
  • If this is a bug fix:
  • Added unit tests if needed
  • Updated unit tests if needed
  • Tests passed when run locally

@theyostalservice theyostalservice force-pushed the patricky/handle_agg_params_correctly branch from a0445cd to 587b5b1 Compare January 18, 2026 21:36
@theyostalservice theyostalservice marked this pull request as ready for review January 18, 2026 21:37
Comment on lines +76 to +77
use_discrete_percentile: True
use_approximate_percentile: False
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YAML 1.2+ requires booleans be lowercase.

Suggested change
use_discrete_percentile: True
use_approximate_percentile: False
use_discrete_percentile: true
use_approximate_percentile: false

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.

3 participants