Detect additional runtimes + track install_id across model calls

[safaricd]

Change Description

With this change, we introduce the following:

• Detect additional runtimes for TabPFN: MLflow, Kubernetes and Modal.
• Track pseudo-anonymous install_id across predict_called and fit_called events.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 enhances the telemetry system by expanding its ability to detect various execution environments, specifically adding support for MLflow, Kubernetes, and Modal. Concurrently, it introduces a mechanism to track a unique, pseudo-anonymous "install_id" across model prediction and fitting events, providing more granular insights into user interactions without compromising privacy.

Highlights

• Runtime Detection Expansion: Added support for detecting MLflow, Kubernetes, and Modal as operational runtimes within the telemetry system.
• Install ID Tracking: Implemented tracking of a pseudo-anonymous "install_id" across "predict_called" and "fit_called" telemetry events to better understand usage patterns.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• src/tabpfn_common_utils/telemetry/core/events.py
  • Added "install_id" field to "ModelCallEvent" to track user installations.
• src/tabpfn_common_utils/telemetry/core/runtime.py
  • Included "modal", "mlflow", and "kubernetes" in the list of "RUNTIME_NAMES".
  • Defined environment variable hints for detecting "modal", "mlflow", and "kubernetes" runtimes.

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. ↩

[gemini-code-assist]

Code Review

This pull request enhances telemetry by detecting additional runtimes (MLflow, Kubernetes, and Modal) and by tracking a pseudo-anonymous install_id across model fit and predict calls. The implementation correctly adds the new runtime environments and their corresponding detection hints. The install_id is now included in ModelCallEvent, ensuring it's captured for fit and predict events, consistent with other telemetry events. The changes are logical and align well with the existing telemetry framework.

[ggprior]

I see, you probe for commonly set environment variables to detect the runtime. Looks good! Thanks for tagging me.