Celery 2.3 Documentation
don’t clutter the history with merging commit notes. See Rebasing merge commits in git [http://notes.envato.com/developers/rebasing-merge-commits-in-git/]. If you want to learn more about rebasing see the the STARTED state: PID and host name of the worker that started the task. See issue #181 subtask: Merge additional keyword arguments to subtask() into task keyword arguments. e.g.: >>> s = subtask((1 either(default_key, *values) Fallback to the value of a configuration key if none of the *values are true. merge(l, r) Like dict(a, **b) except it will keep values from a if the value in b is None. Functions0 码力 | 530 页 | 900.64 KB | 1 年前3Celery 2.4 Documentation
upstream master With this option you don’t clutter the history with merging commit notes. See Rebasing merge commits in git. If you want to learn more about rebasing see the Rebase section in the Github guides STARTED state: PID and host name of the worker that started the task. See issue #181 • subtask: Merge additional keyword arguments to subtask() into task keyword arguments. e.g.: 176 Chapter 9. Change either(default_key, *values) Fallback to the value of a configuration key if none of the *values are true. merge(l, r) Like dict(a, **b) except it will keep values from a if the value in b is None. 10.1.2 Functions0 码力 | 395 页 | 1.54 MB | 1 年前3Celery v5.0.1 Documentation
don’t clutter the history with merging commit notes. See Rebasing merge commits in git [https://notes.envato.com/developers/rebasing-merge-commits-in-git/]. If you want to learn more about rebasing, see with master. It is very important to rebase PRs before they can be merged to master to solve any merge conflicts. Status: Needs Test Coverage Celery uses codecov [https://codecov.io/gh/celery/celery] info(fields=None, extra=None) Information about this task suitable for on-screen display. kwargs = None merge_rules = {'RECEIVED': ('name', 'args', 'kwargs', 'parent_id', 'root_id', 'retries', 'eta', 'expires')}0 码力 | 2313 页 | 2.13 MB | 1 年前3Celery v5.0.2 Documentation
don’t clutter the history with merging commit notes. See Rebasing merge commits in git [https://notes.envato.com/developers/rebasing-merge-commits-in-git/]. If you want to learn more about rebasing, see with master. It is very important to rebase PRs before they can be merged to master to solve any merge conflicts. Status: Needs Test Coverage Celery uses codecov [https://codecov.io/gh/celery/celery] info(fields=None, extra=None) Information about this task suitable for on-screen display. kwargs = None merge_rules = {'RECEIVED': ('name', 'args', 'kwargs', 'parent_id', 'root_id', 'retries', 'eta', 'expires')}0 码力 | 2313 页 | 2.14 MB | 1 年前3Celery v5.0.0 Documentation
don’t clutter the history with merging commit notes. See Rebasing merge commits in git [https://notes.envato.com/developers/rebasing-merge-commits-in-git/]. If you want to learn more about rebasing, see with master. It is very important to rebase PRs before they can be merged to master to solve any merge conflicts. Status: Needs Test Coverage Celery uses codecov [https://codecov.io/gh/celery/celery] info(fields=None, extra=None) Information about this task suitable for on-screen display. kwargs = None merge_rules = {'RECEIVED': ('name', 'args', 'kwargs', 'parent_id', 'root_id', 'retries', 'eta', 'expires')}0 码力 | 2309 页 | 2.13 MB | 1 年前3Celery v5.0.5 Documentation
history with merging commit notes. See Rebasing merge commits in git [https://web.archive.org/web/20150627054345/http://marketblog.envato.com/general/rebasing-merge-commits- in-git/]. If you want to learn more with master. It is very important to rebase PRs before they can be merged to master to solve any merge conflicts. Status: Needs Test Coverage Celery uses codecov [https://codecov.io/gh/celery/celery] info(fields=None, extra=None) Information about this task suitable for on-screen display. kwargs = None merge_rules = {'RECEIVED': ('name', 'args', 'kwargs', 'parent_id', 'root_id', 'retries', 'eta', 'expires')}0 码力 | 2315 页 | 2.14 MB | 1 年前3Celery 2.4 Documentation
don’t clutter the history with merging commit notes. See Rebasing merge commits in git [http://notes.envato.com/developers/rebasing-merge-commits-in-git/]. If you want to learn more about rebasing see the the STARTED state: PID and host name of the worker that started the task. See issue #181 subtask: Merge additional keyword arguments to subtask() into task keyword arguments. e.g.: >>> s = subtask((1 either(default_key, *values) Fallback to the value of a configuration key if none of the *values are true. merge(l, r) Like dict(a, **b) except it will keep values from a if the value in b is None. Functions0 码力 | 543 页 | 957.42 KB | 1 年前3Celery 2.2 Documentation
the STARTED state: PID and host name of the worker that started the task. See issue #181 subtask: Merge additional keyword arguments to subtask() into task keyword arguments. e.g.: >>> s = subtask((1 either(default_key, *values) Fallback to the value of a configuration key if none of the *values are true. merge(l, r) Like dict(a, **b) except it will keep values from a if the value in b is None. Functions on-screen display. merge(state, timestamp, fields) Merge with out of order event. merge_rules = {'RECEIVED': ('name', 'args', 'kwargs', 'retries', 'eta', 'expires')} How to merge out of order events0 码力 | 505 页 | 878.66 KB | 1 年前3Celery 3.0 Documentation
don’t clutter the history with merging commit notes. See Rebasing merge commits in git [http://notes.envato.com/developers/rebasing-merge-commits-in-git/]. If you want to learn more about rebasing see the timestamp, received, fields) Task.update Use Task.event(short_type, timestamp, received, fields) Task.merge Contact us if you need this. Magic keyword arguments Support for the very old magic keyword arguments for on-screen display. kwargs = None merge_rules = {u'RECEIVED': (u'name', u'args', u'kwargs', u'parent_id', u'root_idretries', u'eta', u'expires')} How to merge out of order events. Disorder is detected0 码力 | 2110 页 | 2.23 MB | 1 年前3Celery v4.0.0 Documentation
don’t clutter the history with merging commit notes. See Rebasing merge commits in git [http://notes.envato.com/developers/rebasing-merge-commits-in-git/]. If you want to learn more about rebasing see the timestamp, received, fields) Task.update Use Task.event(short_type, timestamp, received, fields) Task.merge Contact us if you need this. Magic keyword arguments Support for the very old magic keyword arguments for on-screen display. kwargs = None merge_rules = {u'RECEIVED': (u'name', u'args', u'kwargs', u'parent_id', u'root_idretries', u'eta', u'expires')} How to merge out of order events. Disorder is detected0 码力 | 2106 页 | 2.23 MB | 1 年前3
共 47 条
- 1
- 2
- 3
- 4
- 5