[DEL] explicit commits, they are not compatible with queue jobs#136
[DEL] explicit commits, they are not compatible with queue jobs#136OCA-git-bot merged 2 commits intoOCA:16.0from
Conversation
|
Ah, actually the error received is this one: |
|
Thank you @thomaspaulb for this fix. Indeed, it has been done that way initially as one scanner call is able to parse & push multiple modules within the same transaction, but jobs have been processing module one by one now so this force-commit is useless I guess now (and doesn't work anyway as you stated). |
|
@sebalix without this change the module is now not working, so i guess we should approve and merge? |
|
@thomaspaulb I'm not able to reproduce it on my side (I have a 18.0 node running scans every day) , could it be linked to the configuration of ODOO_QUEUE_JOB_CHANNELS: root:4,root.odoo_repository_scan:3,root.odoo_repository_find_pr_url:1,root.odoo_repository_scan_migration:1If you have more info so I could test this PR before merging |
|
@thomaspaulb sorry, I was not up-to-date regarding OCA/queue 👍 Just saw queue#880 which has been backported on 16.0 here. I can reproduce the issue right now. |
|
/ocabot merge patch |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
|
Congratulations, your PR was merged at 77bff0e. Thanks a lot for contributing to OCA. ❤️ |
|
Ah great, you were able to reproduce :) thanks for merging! |
This is more of a discussion point, I think bluntly deleting this commit statements is maybe not the solution, perhaps we need to check if the methods are run via a queue job or not? Via the context? (Either by the context keys that queue_job injects itself, or by adding an explicit one)
@gjotten Do you remember which error you got? Scouring the logfile yields a couple of "Cursor already closed" errors, maybe it was that one?