15:37 this is not a good pattern you shouldn't call a task from another task that way. I would be better to create a workflow where check_url raises an error when spam is found and take_some_action is bound to the on_error task method of check_url. ex: # in the caller check_url.s(id, url).on_error(take_some_action.s(id, url)).delay()
this is from 8 years ago. a lot has changed, in technology, business, etc. does insta still use Celery?
Watch it just now, still awesome!❤
great talk thank you!
Enjoyed this very much, thank you!
15:37 this is not a good pattern you shouldn't call a task from another task that way. I would be better to create a workflow where check_url raises an error when spam is found and take_some_action is bound to the on_error task method of check_url. ex:
# in the caller
check_url.s(id, url).on_error(take_some_action.s(id, url)).delay()
Great talk. Thanks!
No BS, to the point talk. Awesome.
i love this stuff!
How does he get rid of the SHIM?
Great talk, but still don't get what this chained task thing is ..
I think thats a simple recursive batch execution. The completion of the one batch triggers next with an offset.
think of it as pagination
9:30
Is redis user ID list unbounded and ever increasing
that's great :+1
5:29