-
-
Notifications
You must be signed in to change notification settings - Fork 551
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base_tier_validation: blocking notifications cron, a.k.a. should it block sudo writes? #875
Labels
Comments
I think the block is not happening when writting access_token because when performing a validation, this functions must be called and access_token is allowed to be written |
Ah good catch! Then the problem must be around these lines:
|
yajo
added a commit
to moduon/delivery-carrier
that referenced
this issue
May 8, 2024
Fix OCA/server-ux#875 by actually implementing this sentence: https://github.com/OCA/delivery-carrier/blob/3a93f81bf3038e6ccb7fba4ce49376fe4f1422ee/delivery_auto_refresh/readme/DESCRIPTION.rst?plain=1#L3-L4 Now, auto-refreshing will be triggered only when modifying SO lines. Any other modifications will pass normally. @moduon MT-5997
Then this should be the real fix: OCA/delivery-carrier#815 |
Fixed by OCA/delivery-carrier#799. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Module
base_tier_validation
Describe the bug
We have a database where
base_tier_validation
is installed along with other addons from its family.The cron
mail.ir_cron_send_scheduled_message
is blocked in loop because of that addon.To Reproduce
Affected versions: 16.0 and probably others.
Steps to reproduce the behavior:
Actual behavior
Cron enters fail loop. Traceback:
Expected behavior
Cron should work. Notifications should be sent, no matter the validation status.
Additional context
A possibility to fix the problem would be:
portal
to the dependencies ofbase_tier_validation
_portal_ensure_token()
.with_context(skip_validation_check=True)
However, pay attention to this part of the traceback:
As you can see, the token is being written with sudo. I think it's a bug to block writes in sudo.
@moduon MT-5997
The text was updated successfully, but these errors were encountered: