Skip to content

fix: resolve CI failures on 19.0 branch#48

Merged
jeremi merged 3 commits into19.0from
fix/ci-failures-19.0
Feb 17, 2026
Merged

fix: resolve CI failures on 19.0 branch#48
jeremi merged 3 commits into19.0from
fix/ci-failures-19.0

Conversation

@jeremi
Copy link
Copy Markdown
Member

@jeremi jeremi commented Feb 17, 2026

Summary

  • fix(spp_change_request_v2): Move _() translation calls out of return dict literals into local variables — in Odoo 19, _() inspects the call stack for a valid cursor, which fails when called inline in a return statement. Also fix test assertions to match actual ir.actions.client return structure.
  • fix(spp_key_management, spp_claim_169): Add missing jwcrypto to external_dependencies in both manifests and to requirements.txt for CI installation. Without this, tests exercising key generation paths fail.
  • fix(spp_drims_sl_demo): Run prettier on XML data files to fix attribute formatting. Convert three GeoJSON files from raw content to proper Git LFS pointers.

Test plan

  • CI pre-commit check passes (XML formatting + LFS pointers)
  • spp_change_request_v2 tests pass (specifically test_wizard_create_draft_success)
  • spp_mis_demo_v2 tests pass (specifically test_claim169_* tests)
  • Full Test Suite build job passes (once runner disk space is cleared)

…e wizard

Move _() translation calls out of return dict literals into local
variables. In Odoo 19, _() inspects the call stack to find a valid
cursor, which can fail when called inline in a return statement.

Also fix test assertions to match actual ir.actions.client return
structure instead of ir.actions.act_window.
Add jwcrypto to external_dependencies in both spp_key_management and
spp_claim_169 manifests, and to requirements.txt for CI installation.

Without this, tests exercising key generation paths fail with
"jwcrypto library required for key generation".
…ointers

Run prettier on XML data files to fix attribute formatting.
Convert three GeoJSON files from raw content to proper Git LFS
pointers as specified by .gitattributes.
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @jeremi, 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 critical CI failures on the 19.0 branch by implementing several fixes across different modules. The changes primarily focus on ensuring compatibility with Odoo 19's behavior regarding translation calls, resolving missing external dependencies for cryptographic operations, and standardizing data file formatting and storage. These updates are essential for maintaining a stable and functional development environment.

Highlights

  • Odoo 19 Compatibility: Resolved issues with _() translation calls in Odoo 19 by moving them out of return dict literals and updated test assertions to match the new ir.actions.client return structure.
  • Dependency Management: Added the jwcrypto library to requirements.txt and relevant __manifest__.py files to ensure proper installation for key generation functionalities.
  • Code Formatting and LFS: Applied Prettier formatting to several XML data files and converted GeoJSON files to Git LFS pointers for better repository management.
Changelog
  • requirements.txt
    • Added jwcrypto to the list of required Python packages.
  • spp_change_request_v2/tests/test_ux_wizards.py
    • Updated test assertions to correctly validate the ir.actions.client return structure.
  • spp_change_request_v2/wizards/create_wizard.py
    • Refactored _() translation calls to local variables to prevent failures when used within return dict literals in Odoo 19.
  • spp_claim_169/manifest.py
    • Included jwcrypto in the external_dependencies list.
  • spp_drims_sl_demo/data/demo_gis_reports.xml
    • Applied Prettier formatting to XML attributes.
  • spp_drims_sl_demo/data/demo_products.xml
    • Applied Prettier formatting to XML attributes.
  • spp_drims_sl_demo/data/demo_users.xml
    • Applied Prettier formatting to XML attributes.
  • spp_drims_sl_demo/wizard/demo_generator_views.xml
    • Applied Prettier formatting to XML attributes.
  • spp_key_management/manifest.py
    • Included jwcrypto in the external_dependencies list.
Activity
  • CI pre-commit check passes (XML formatting + LFS pointers)
  • spp_change_request_v2 tests pass (specifically test_wizard_create_draft_success)
  • spp_mis_demo_v2 tests pass (specifically test_claim169_* tests)
  • Full Test Suite build job passes (once runner disk space is cleared)
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
Copy Markdown

@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 introduces several fixes to resolve CI failures. The changes include moving Odoo translation calls to local variables to prevent call stack issues in Odoo 19, adding the missing jwcrypto dependency to manifests and requirements.txt, and applying consistent formatting to several XML data files. The code changes are correct and well-implemented, particularly the fix for the translation calls which is clearly explained. The test updates accurately reflect the new return structure. The dependency and formatting changes are also appropriate. The pull request is in good shape and addresses the stated goals effectively.

@jeremi jeremi merged commit 1f06116 into 19.0 Feb 17, 2026
26 of 27 checks passed
@jeremi jeremi deleted the fix/ci-failures-19.0 branch February 17, 2026 06:50
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.

1 participant