Skip to content

Conversation

@florentx florentx changed the base branch from 16.0 to 15.0 December 27, 2024 10:09
@florentx florentx force-pushed the 15.0_port branch 3 times, most recently from 860fa99 to 88df44d Compare December 27, 2024 13:03
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 27, 2025
@florentx
Copy link
Contributor Author

florentx commented May 8, 2025

Hi, can you merge this PR, and/or remove the stale label?

Also PR #731
Thank you.
@guewen / @sbidoul

sebalix and others added 14 commits May 8, 2025 13:12
By default, odoo never runs the same cron job in parallel. This commit uses the identity key mechanism to enforce this mechanism when a cron job is run as a queue job. This behaviour can be controlled by a new setting on the cron definition but is activated by default to keep the original behaviour
Configuration of randomized retry intervals is not possible due to the formatting checks not being updated.
This should fix it.
* use FIFO, firt createad job will be treat first
* if priority are different it take the precedent

Yet we are not using channel priority into account
Current situation:

* multiple keys for no good reason
* half baked: not all of them used everywhere
* no centralization
* poor naming

With this change we'll have:

* 1 and only one key to disable via ctx: ``queue_job__no_delay``
* 1 and only one key to disable via os env: ``QUEUE_JOB__NO_DELAY``
* backward compatibility with deprecation for old keys
Otherwise, you cannot use any channel other than default (
root.ir_cron)
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label May 11, 2025
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 14, 2025
@github-actions github-actions bot closed this Oct 19, 2025
@sbidoul sbidoul reopened this Dec 30, 2025
@OCA-git-bot
Copy link
Contributor

Hi @guewen, @ivantodorovich,
some modules you are maintaining are being modified, check this out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.