Odoo Changelog — 2026-09-22

Tuesday, September 22, 2026

2 changes · saas-19.2

Improvements(2)

Enhancements to existing features

[PERF] base: cache barcode/QR PNG rendering with cache

Coresaas-19.2baseMedium

Repeated barcodes and QR codes in large reports are now reused during report generation instead of being recreated each time. This can dramatically reduce processing time for long documents with repeated codes, making report generation much faster without changing the report output.

Original PR description

### Description of the issue/feature this PR addresses: Reports with hundreds of pages and repeated barcodes or QR codes (same document number, same lot code on every page) re-run reportlab's…

### Description of the issue/feature this PR addresses:

Reports with hundreds of pages and repeated barcodes or QR codes (same document number, same lot code on every page) re-run reportlab's createBarcodeDrawing and PNG encoding on every occurrence, even when type, value and options are identical.

### Current behavior before PR:

Every call to ir.actions.report.barcode() re-renders the barcode/QR from scratch, regardless of whether an identical (type, value, options) combination was already rendered earlier in the same report. On a 900-page report with 4 barcodes/page, this dominates generation time.

Benchmark, 900 pages x 4 barcodes/page, 4 distinct combos, 3600 calls: 19.131s.

### Desired behavior after PR is merged:

The pure rendering step (createBarcodeDrawing + mask + PNG encoding) is extracted to a module-level function keyed on (barcode_type, value, options, mask) and wrapped with functools.lru_cache. Repeated barcodes reuse the cached PNG instead of re-rendering.

Same benchmark after the fix: 0.020s (946.7x speedup, cache_info hits=3596 misses=4).







---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#289261
Forward-Port-Of: odoo/odoo#289135

#performance#reports#barcodes#qr-codes

[IMP] iap: add sticky notification when IAP down

PR #289715

Coresaas-19.2iapMedium

Users will now see a persistent notification when the IAP service is down. This helps them understand that related actions may not work temporarily due to a service outage rather than a problem with their setup.

Original PR description

We wanted to let the user know when the IAP server is down with a sticky notification.

Task-6570098

Forward-Port-Of: odoo/odoo#289599
Forward-Port-Of: odoo/odoo#288098

#notification#service availability#iap

### Description of the issue/feature this PR addresses: Reports with hundreds of pages and repeated barcodes or QR codes (same document number, same lot code on every page) re-run reportlab's createBarcodeDrawing and PNG encoding on every occurrence, even when type, value and options are identical. ### Current behavior before PR: Every call to ir.actions.report.barcode() re-renders the barcode/QR from scratch, regardless of whether an identical (type, value, options) combination was already rendered earlier in the same report. On a 900-page report with 4 barcodes/page, this dominates generation time. Benchmark, 900 pages x 4 barcodes/page, 4 distinct combos, 3600 calls: 19.131s. ### Desired behavior after PR is merged: The pure rendering step (createBarcodeDrawing + mask + PNG encoding) is extracted to a module-level function keyed on (barcode_type, value, options, mask) and wrapped with functools.lru_cache. Repeated barcodes reuse the cached PNG instead of re-rendering. Same benchmark after the fix: 0.020s (946.7x speedup, cache_info hits=3596 misses=4). --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#289261 Forward-Port-Of: odoo/odoo#289135