Skip to content

[CI] Fix doctest job by pinning ipython to 9.9.0#5221

Closed
vfdev-5 wants to merge 3 commits intomainfrom
fix-doctest
Closed

[CI] Fix doctest job by pinning ipython to 9.9.0#5221
vfdev-5 wants to merge 3 commits intomainfrom
fix-doctest

Conversation

@vfdev-5
Copy link
Collaborator

@vfdev-5 vfdev-5 commented Feb 3, 2026

Inspecting logs of failed job vs passing job, here is the python packages version difference:

Package Log 1 - Fail (Feb 3) Log 2 - Pass (Jan 30) Difference
ipython 9.10.0 9.9.0 +0.1.0
rich 14.3.2 14.3.1 +0.0.1
wcwidth 0.5.3 0.5.2 +0.0.1
wrapt 2.1.1 2.0.1 +0.1.0
coverage 7.13.3 7.13.2 +0.0.1
babel 2.18.0 2.17.0 +0.1.0
numpy (final) 2.4.2 2.4.1 +0.0.1

Source: https://www.kimi.com/share/19c249cb-3362-81a6-8000-00006b942ed6

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @vfdev-5, 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 addresses a doctest failure by specifying a precise version for the ipykernel dependency. By pinning ipykernel to version 9.9.0 in the pyproject.toml file, the PR ensures that the testing environment uses a known compatible version, thereby resolving the reported doctest issues and maintaining build stability.

Highlights

  • Dependency Pinning: The ipykernel dependency in pyproject.toml has been explicitly pinned to version 9.9.0.
  • Doctest Fix: This change is intended to resolve a doctest failure, suggesting an incompatibility with a different ipykernel version.

🧠 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
  • pyproject.toml
    • Pinned the ipykernel dependency to version 9.9.0 to fix doctest failures.
Activity
  • No human activity has been recorded on this pull request yet.
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
Contributor

@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 pins the ipykernel dependency to version 9.9.0 in pyproject.toml, which is a common practice to fix issues like the one mentioned in the title ("Fix doctest") and ensure a stable environment. I've added one suggestion to include an inline comment explaining the version pin, which will improve code maintainability for future developers.

@vfdev-5 vfdev-5 changed the title Fix doctest [CI] Fix doctest job by pinning ipython to 9.9.0 Feb 3, 2026
@vfdev-5 vfdev-5 marked this pull request as ready for review February 3, 2026 22:11
@vfdev-5 vfdev-5 marked this pull request as draft February 3, 2026 22:12
@samanklesaria
Copy link
Collaborator

Superceeded by #5222

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