Celery 3.0 Documentationwhether this step should be created. info(obj)[source] instantiate(name, *args, **kwargs)[source] label = None Optional short name used for graph outputs and in logs. last = False This flag is reserved set([u'redis', u'amqp']) election(id, topic, action=None)[source] get_consumers(channel)[source] label = u'Gossip' name = u'celery.worker.consumer.gossip.Gossip' on_elect(event)[source] on_elect_ack(event)[source] revoked tasks. compatible_transport(app)[source] compatible_transports = set([u'redis', u'amqp']) label = u'Mingle' name = u'celery.worker.consumer.mingle.Mingle' on_clock_event(c, clock)[source] on_node_reply(c0 码力 | 2110 页 | 2.23 MB | 1 年前3
Celery v4.0.0 Documentationwhether this step should be created. info(obj)[source] instantiate(name, *args, **kwargs)[source] label = None Optional short name used for graph outputs and in logs. last = False This flag is reserved set([u'redis', u'amqp']) election(id, topic, action=None)[source] get_consumers(channel)[source] label = u'Gossip' name = u'celery.worker.consumer.gossip.Gossip' on_elect(event)[source] on_elect_ack(event)[source] revoked tasks. compatible_transport(app)[source] compatible_transports = set([u'redis', u'amqp']) label = u'Mingle' name = u'celery.worker.consumer.mingle.Mingle' on_clock_event(c, clock)[source] on_node_reply(c0 码力 | 2106 页 | 2.23 MB | 1 年前3
Celery 4.4.2 DocumentationMake sure any change or new feature has a unit and/or integration test. If a test is not written, a label will be assigned to your PR with the name Needs Test Coverage. • [ ] Make sure unit test coverage issue with important details. For instance, you might see a Component:canvas label on an issue or PR. The Component:canvas label means the issue or PR corresponds to the canvas functionality. These labels Celery uses codecov to verify code coverage. Please make sure PRs do not decrease code coverage. This label will identify PRs which need code coverage. • Status: Needs Test Case The issue or PR needs a test0 码力 | 797 页 | 2.85 MB | 1 年前3
Celery v4.3.0 DocumentationMake sure any change or new feature has a unit and/or integration test. If a test is not written a label will be assigned to your PR with the name Needs Test Coverage. • [ ] Make sure unit test coverage issue with important details. For instance, you might see a Component:canvas label on an issue or PR. The Component:canvas label means the issue or PR corresponds to the canvas functionality. These labels uses codecov _ to verify code coverage. Please, make sure PRs do not decrease code coverage. This label will identify PRs which need code coverage. • Status: Needs Test Case The issue or PR needs a test0 码力 | 790 页 | 2.84 MB | 1 年前3
Celery 4.4.1 DocumentationMake sure any change or new feature has a unit and/or integration test. If a test is not written, a label will be assigned to your PR with the name Needs Test Coverage. • [ ] Make sure unit test coverage issue with important details. For instance, you might see a Component:canvas label on an issue or PR. The Component:canvas label means the issue or PR corresponds to the canvas functionality. These labels Celery uses codecov to verify code coverage. Please make sure PRs do not decrease code coverage. This label will identify PRs which need code coverage. • Status: Needs Test Case The issue or PR needs a test0 码力 | 797 页 | 2.85 MB | 1 年前3
Celery 4.4.0 DocumentationMake sure any change or new feature has a unit and/or integration test. If a test is not written, a label will be assigned to your PR with the name Needs Test Coverage. • [ ] Make sure unit test coverage issue with important details. For instance, you might see a Component:canvas label on an issue or PR. The Component:canvas label means the issue or PR corresponds to the canvas functionality. These labels Celery uses codecov to verify code coverage. Please make sure PRs do not decrease code coverage. This label will identify PRs which need code coverage. • Status: Needs Test Case The issue or PR needs a test0 码力 | 795 页 | 2.84 MB | 1 年前3
Celery 3.1 Documentationthat decides whether this step should be created. info(obj) instantiate(name, *args, **kwargs) label = None Optional short name used for graph outputs and in logs. last = False This flag is reserved Connection{()},)},)},) shutdown(c) start(c) stop(c) class celery.worker.consumer.Evloop(parent, **kwargs) label = ‘event loop’ last = True name = u’celery.worker.consumer.Evloop’ 362 Chapter 2. Contents Celery without_mingle=False, **kwargs) compatible_transport(app) compatible_transports = set([’redis’, ‘amqp’]) label = ‘Mingle’ name = u’celery.worker.consumer.Mingle’ requires = (step:celery.worker.consumer.Events{(step:celery0 码力 | 607 页 | 2.27 MB | 1 年前3
Celery v5.0.1 DocumentationMake sure any change or new feature has a unit and/or integration test. If a test is not written, a label will be assigned to your PR with the name Needs Test Coverage. [ ] Make sure unit test coverage does issue with important details. For instance, you might see a Component:canvas label on an issue or PR. The Component:canvas label means the issue or PR corresponds to the canvas functionality. These labels io/gh/celery/celery] to verify code coverage. Please make sure PRs do not decrease code coverage. This label will identify PRs which need code coverage. Status: Needs Test Case The issue or PR needs a test0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.2 DocumentationMake sure any change or new feature has a unit and/or integration test. If a test is not written, a label will be assigned to your PR with the name Needs Test Coverage. [ ] Make sure unit test coverage does issue with important details. For instance, you might see a Component:canvas label on an issue or PR. The Component:canvas label means the issue or PR corresponds to the canvas functionality. These labels io/gh/celery/celery] to verify code coverage. Please make sure PRs do not decrease code coverage. This label will identify PRs which need code coverage. Status: Needs Test Case The issue or PR needs a test0 码力 | 2313 页 | 2.14 MB | 1 年前3
Celery v5.0.0 DocumentationMake sure any change or new feature has a unit and/or integration test. If a test is not written, a label will be assigned to your PR with the name Needs Test Coverage. [ ] Make sure unit test coverage does issue with important details. For instance, you might see a Component:canvas label on an issue or PR. The Component:canvas label means the issue or PR corresponds to the canvas functionality. These labels io/gh/celery/celery] to verify code coverage. Please make sure PRs do not decrease code coverage. This label will identify PRs which need code coverage. Status: Needs Test Case The issue or PR needs a test0 码力 | 2309 页 | 2.13 MB | 1 年前3
共 37 条
- 1
- 2
- 3
- 4













