You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 29, 2023. It is now read-only.
The current implementation of deferred tasks tries always to get the current user and run the task with the associated credentials.
It would be nice to have the chance to control this behavior. E.g. to have the possibility to run a task anonym.
My proposal is to introduce an optional parameter user with this you can submit a user or None to run with specific or without any credentials.
Maybe this could be also interesting for the language.
The text was updated successfully, but these errors were encountered:
The current implementation of deferred tasks tries always to get the current user and run the task with the associated credentials.
It would be nice to have the chance to control this behavior. E.g. to have the possibility to run a task anonym.
My proposal is to introduce an optional parameter
user
with this you can submit a user orNone
to run with specific or without any credentials.Maybe this could be also interesting for the language.
The text was updated successfully, but these errors were encountered: