Skip to content
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

[13.0][FIX] queue_job: recompute with user #649

Closed

Conversation

vincent-hatakeyama
Copy link
Contributor

When queue_job is not used, recomputing is done with the same user that did the changes.
queue_job changes that and the superuser is used instead. That causes problems. For example, when mail are sent, if the superuser has no mail address.

After this change, the original user is used instead of the superuser.

Goes after #648

sebalix and others added 2 commits May 17, 2024 09:52
So the time required to compute such fields by the ORM is taken into
account when the 'date_done' and 'exec_time' values are set on the job.
When queue_job is not used, recomputing is done with the same user that
did the changes.
queue_job changes that and the superuser is used instead. That causes
problems. For example, when mail are sent, if the superuser has no mail
address.

After this change, the original user is used instead of the superuser.
@OCA-git-bot
Copy link
Contributor

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

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 15, 2024
@github-actions github-actions bot closed this Oct 20, 2024
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.

3 participants