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
As @wojcikstefan pointed out, a task t(x) would have a different ID used for uniqueness and locking depending on whether it was used queued as t(x=1) or t(1), since the arg would either be in args or in kwargs.
As @wojcikstefan pointed out, a task
t(x)
would have a different ID used for uniqueness and locking depending on whether it was used queued ast(x=1)
ort(1)
, since the arg would either be inargs
or inkwargs
.This applies to
unique
andlock_key
(see e.g. https://github.com/closeio/tasktiger/blob/master/tasktiger/worker.py#L820-L825).We should find a way to normalize the task lock IDs.
The text was updated successfully, but these errors were encountered: