Skip to content

Conversation

charleskorn
Copy link
Contributor

@charleskorn charleskorn commented Mar 7, 2025

What this PR does

This PR upgrades mimir-prometheus to include the changes from grafana/mimir-prometheus#837.

I've added a changelog entry for one of the fixes in that set of changes, however the remainder don't seem worthy of a changelog entry (eg. because they're not relevant for Mimir, or are for experimental native histograms).

I've tried to build up this PR incrementally. I would suggest reviewing each commit separately.

Which issue(s) this PR fixes or relates to

(none)

Checklist

  • Tests updated.
  • [n/a] Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • [n/a] about-versioning.md updated with experimental features.

@charleskorn charleskorn force-pushed the charleskorn/upgrade-prometheus branch 2 times, most recently from 71c0ab9 to 6f913d7 Compare March 12, 2025 00:22
@charleskorn charleskorn force-pushed the charleskorn/upgrade-prometheus branch from 50c217f to 001ae48 Compare March 12, 2025 00:43
@charleskorn charleskorn marked this pull request as ready for review March 12, 2025 00:57
@charleskorn charleskorn requested review from stevesg, grafanabot and a team as code owners March 12, 2025 00:57
Copy link
Contributor

@jhesketh jhesketh left a comment

Choose a reason for hiding this comment

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

lgtm, thanks for working on this! Just one new change that I don't think is adequately tested.

},
},
}

Copy link
Contributor

Choose a reason for hiding this comment

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

What about a test case for when the second last point and last point change types, and don't change types (in both orders)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is quite difficult to test completely due to prometheus/prometheus#14172.

The test cases added upstream and included in this PR should cover most of the scenarios: float then float, float then histogram and histogram then histogram. Histogram then float is blocked by prometheus/prometheus#14172.

Are there other scenarios you had in mind?

Copy link
Contributor

Choose a reason for hiding this comment

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

I missed those, thanks. lgtm

@charleskorn charleskorn merged commit 7e533c9 into main Mar 12, 2025
28 checks passed
@charleskorn charleskorn deleted the charleskorn/upgrade-prometheus branch March 12, 2025 02:28
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