Celery v5.0.1 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.2 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2313 页 | 2.14 MB | 1 年前3
Celery v5.0.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2309 页 | 2.13 MB | 1 年前3
Celery v5.0.5 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an track of this for us. task = state.tasks.get(event['uuid']) print('TASK FAILED: %s[%s] %s' % ( task.name, task.uuid, task.info(),)) with app.connection() as connection:0 码力 | 2315 页 | 2.14 MB | 1 年前3
Celery 3.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID), this is the task id. The delay and apply_async methods return an AsyncResult instance, that can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2110 页 | 2.23 MB | 1 年前3
Celery v4.0.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID), this is the task id. The delay and apply_async methods return an AsyncResult instance, that can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2106 页 | 2.23 MB | 1 年前3
Celery 2.1 DocumentationTrace- backs Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to execute it with and some additional metadata – like the number of retries or an arguments. Task Events • task-received(uuid, name, args, kwargs, retries, eta, hostname, timestamp) Sent when the worker receives a task. • task-started(uuid, hostname, timestamp) Sent just before0 码力 | 285 页 | 1.19 MB | 1 年前3
Celery 2.1 DocumentationTracebacks Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to execute it with and some additional metadata – like the number of retries or an their arguments. Task Events task-received(uuid, name, args, kwargs, retries, eta, hostname, timestamp) Sent when the worker receives a task. task-started(uuid, hostname, timestamp) Sent just before the0 码力 | 463 页 | 861.69 KB | 1 年前3
Celery 2.2 DocumentationTrace- backs Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and return r = [] setid = gen_unique_id() for task in tasks: uuid = gen_unique_id() task.options["task_id"] = uuid r.append((task, current_app.AsyncResult(uuid))) ts = current_app.TaskSetResult(setid, [task[1] for format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to execute it with and some additional metadata – like the number of retries or an0 码力 | 314 页 | 1.26 MB | 1 年前3
Celery v4.0.1 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID), this is the task id. The delay and apply_async methods return an AsyncResult instance, that can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 1040 页 | 1.37 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













