python/python-celery
SHA256
15
0
Fork 0
forked from pool/python-celery
Code Pull Requests Activity

- Update to 3.0.14:

Browse Source 
- Now depends on Kombu 2.5.6
  - Now depends on billiard 2.7.3.20
  - execv is now disabled by default.
    It was causing too many problems for users, you can still enable
    it using the CELERYD_FORCE_EXECV setting.
    execv was only enabled when transports other than amqp/redis was used,
    and it's there to prevent deadlocks caused by mutexes not being released
    before the process forks.  Sadly it also changes the environment
    introducing many corner case bugs that is hard to fix without adding
    horrible hacks.  Deadlock issues are reported far less often than the
    bugs that execv are causing, so we now disable it by default.
    Work is in motion to create non-blocking versions of these transports
    so that execv is not necessary (which is the situation with the amqp
    and redis broker transports)
  - Chord exception behavior defined (Issue #1172).
    From Celery 3.1 the chord callback will change state to FAILURE
    when a task part of a chord raises an exception.
    It was never documented what happens in this case,
    and the actual behavior was very unsatisfactory, indeed
    it will just forward the exception value to the chord callback.
    For backward compatibility reasons we do not change to the new
    behavior in a bugfix release, even if the current behavior was
    never documented.  Instead you can enable the
    CELERY_CHORD_PROPAGATES setting to get the new behavior
    that will be default from Celery 3.1.
    See more at chord-errors.
  - worker: Fixes bug with ignored and retried tasks.
    The on_chord_part_return and Task.after_return callbacks,
    nor the task_postrun signal should be called when the task was

OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-celery?expand=0&rev=75
This commit is contained in:
Alexandre Rogoski
2013-02-08 20:24:43 +00:00
committed by Git OBS Bridge
parent f776f7ac60
commit f2d8904592
4 changed files with 81 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

75
python-celery.changes
View File

@@ -1,3 +1,78 @@
-------------------------------------------------------------------
Fri Feb 8 20:10:26 UTC 2013 - alexandre@exatati.com.br
- Update to 3.0.14:
- Now depends on Kombu 2.5.6
- Now depends on billiard 2.7.3.20
- execv is now disabled by default.
It was causing too many problems for users, you can still enable
it using the CELERYD_FORCE_EXECV setting.
execv was only enabled when transports other than amqp/redis was used,
and it's there to prevent deadlocks caused by mutexes not being released
before the process forks. Sadly it also changes the environment
introducing many corner case bugs that is hard to fix without adding
horrible hacks. Deadlock issues are reported far less often than the
bugs that execv are causing, so we now disable it by default.
Work is in motion to create non-blocking versions of these transports
so that execv is not necessary (which is the situation with the amqp
and redis broker transports)
- Chord exception behavior defined (Issue #1172).
From Celery 3.1 the chord callback will change state to FAILURE
when a task part of a chord raises an exception.
It was never documented what happens in this case,
and the actual behavior was very unsatisfactory, indeed
it will just forward the exception value to the chord callback.
For backward compatibility reasons we do not change to the new
behavior in a bugfix release, even if the current behavior was
never documented. Instead you can enable the
CELERY_CHORD_PROPAGATES setting to get the new behavior
that will be default from Celery 3.1.
See more at chord-errors.
- worker: Fixes bug with ignored and retried tasks.
The on_chord_part_return and Task.after_return callbacks,
nor the task_postrun signal should be called when the task was
retried/ignored.
Fix contributed by Vlad.
- GroupResult.join_native now respects the propagate argument.
- subtask.id added as an alias to subtask['options'].id
>>> s = add.s(2, 2)
>>> s.id = 'my-id'
>>> s['options']
{'task_id': 'my-id'}
>>> s.id
'my-id'
- worker: Fixed error `Could not start worker processes` occurring
when restarting after connection failure (Issue #1118).
- Adds new signal task-retried (Issue #1169).
- `celery events --dumper` now handles connection loss.
- Will now retry sending the task-sent event in case of connection failure.
- amqp backend: Now uses Message.requeue instead of republishing
the message after poll.
- New BROKER_HEARTBEAT_CHECKRATE setting introduced to modify the
rate at which broker connection heartbeats are monitored.
The default value was also changed from 3.0 to 2.0.
- celery.events.state.State is now pickleable.
Fix contributed by Mher Movsisyan.
- celery.datastructures.LRUCache is now pickleable.
Fix contributed by Mher Movsisyan.
- The stats broadcast command now includes the workers pid.
Contributed by Mher Movsisyan.
- New conf remote control command to get a workers current configuration.
Contributed by Mher Movsisyan.
- Adds the ability to modify the chord unlock task's countdown
argument (Issue #1146).
Contributed by Jun Sakai
- beat: The scheduler now uses the now() method of the schedule,
so that schedules can provide a custom way to get the current date and time.
Contributed by Raphaël Slinckx
- Fixed pickling of configuration modules on Windows or when execv is used
(Issue #1126).
- Multiprocessing logger is now configured with loglevel ERROR
by default.
Since 3.0 the multiprocessing loggers were disabled by default
(only configured when the MP_LOG environment variable was set).
-------------------------------------------------------------------
Mon Jan 7 16:34:24 UTC 2013 - alexandre@exatati.com.br