Skip to content

Conversation

@devendra-lohar
Copy link
Contributor

@devendra-lohar devendra-lohar commented Dec 8, 2025

This PR prepares new release.

The new changes for the release now fixes CognitePusher to handle late-registered Prometheus metrics (like python_gc_* and python_info). These were earlier causing "Time series not found" errors. The pusher now uses TimeSeriesUploadQueue to automatically create timeseries on-demand when datapoints are pushed.

@devendra-lohar devendra-lohar requested a review from a team as a code owner December 8, 2025 06:21
@gemini-code-assist
Copy link

Summary of Changes

Hello @devendra-lohar, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request prepares for the release of version 7.11.1, primarily addressing a critical fix within the CognitePusher component. The update ensures that the pusher can gracefully handle Prometheus metrics that are registered late by automatically creating any missing timeseries on demand, thereby preventing runtime errors.

Highlights

  • Version Update: The project version has been updated to 7.11.1 across __init__.py and pyproject.toml.
  • CognitePusher Fix: The CognitePusher now automatically creates timeseries for late-registered Prometheus metrics (like python_gc_* and python_info), resolving 'Time series not found' errors.
  • Changelog Entry: A new entry has been added to CHANGELOG.md detailing the fix for CognitePusher in version 7.11.1.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request prepares the 7.11.1 release. The changes consist of version bumps in pyproject.toml and cognite/extractorutils/__init__.py, and an update to CHANGELOG.md. The changelog correctly describes the included fix for CognitePusher to handle late-registered metrics, which is a valuable improvement. The changes are consistent and appropriate for a patch release. This PR looks good to merge.

@codecov
Copy link

codecov bot commented Dec 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.98%. Comparing base (4311e2d) to head (a035b02).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #496   +/-   ##
=======================================
  Coverage   80.98%   80.98%           
=======================================
  Files          43       43           
  Lines        4203     4203           
=======================================
  Hits         3404     3404           
  Misses        799      799           
Files with missing lines Coverage Δ
cognite/extractorutils/__init__.py 100.00% <100.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@Hmnt39 Hmnt39 left a comment

Choose a reason for hiding this comment

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

LGTM

@devendra-lohar devendra-lohar added the waiting-for-risk-review Waiting for a member of the risk review team to take an action label Dec 8, 2025
@rsjr rsjr added the risk-review-ongoing Risk review is in progress label Dec 8, 2025
@rsjr rsjr self-assigned this Dec 8, 2025
@rsjr
Copy link
Contributor

rsjr commented Dec 8, 2025

risk review ok

@rsjr rsjr added waiting-for-team Waiting for the submitter or reviewer of the PR to take an action and removed risk-review-ongoing Risk review is in progress labels Dec 8, 2025
@devendra-lohar devendra-lohar merged commit e1538d0 into master Dec 8, 2025
6 checks passed
@devendra-lohar devendra-lohar deleted the chore/new_release branch December 8, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-for-risk-review Waiting for a member of the risk review team to take an action waiting-for-team Waiting for the submitter or reviewer of the PR to take an action

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants