a754a0e3cbAccepting request 1185136 from home:mcalabkova:branches:devel:languages:python
devel
Dirk Mueller2024-07-04 07:06:05 +00:00
1cba089d59Accepting request 1145321 from devel:languages:pythonAna Guerrero2024-02-09 22:53:40 +00:00
c893ced983- Update to 5.3.6: * Update task.py get_custom_headers missing 'compression' key * Basic ElasticSearch / ElasticClient 8.x Support * Fix eager tasks does not populate name field * Fix: serialization error when gossip working * Stamping bugfix with group/chord header errback linking * Fixed issue: Flags broker_connection_retry_on_startup & broker_connection_retry aren’t reliable * Use string value for CELERY_SKIP_CHECKS envvar * Added initial support for python 3.11 * Fixed a small float value of retry_backoff * Update CELERY_TASK_EAGER setting in user guide * Fixed bug where retrying a task loses its stamps * Warn when an unnamed periodic task override another one. * Fix Task.handle_ignore not wrapping exceptions properly * Align revoke and revoke_by_stamped_headers return values (terminate=True) * Added signal triggered before fork * Deprecate pytz and use zoneinfo * recreate_module: set spec to the new module * Do not recommend using easy_install anymore * importlib_metadata remove deprecated entry point interfaces * New control command revoke_by_stamped_headers * Remove reference to old Python version * Stamping a task left the task properties dirty * Bugfix for nested group stamping on task replace * Add broker_channel_error_retry option * async chords should pass it's kwargs to the group/body. * Fix honor Django's TIME_ZONE setting. * Remove Python 3.4 compatibility code. * Use importlib instead of deprecated pkg_resources.Steve Kowalik2024-02-09 03:10:11 +00:00
d7f18d20b5- Update to 5.02: * Fix _autodiscover_tasks_from_fixups (#6424). * Flush worker prints, notably the banner (#6432). * Breaking Change: Remove ha_policy from queue definition. (#6440) * This argument has no effect since RabbitMQ 3.0. Therefore, We feel comfortable dropping it in a patch release. * Python 3.9 support (#6418). * Regression: When using the prefork pool, pick the fair scheduling strategy by default (#6447). * Preserve callbacks when replacing a task with a chain (#6189). * Fix max_retries override on self.retry() (#6436). * Raise proper error when replacing with an empty chain (#6452) * Specify UTF-8 as the encoding for log files (#6357). * Custom headers now propagate when using the protocol 1 hybrid messages (#6374). * Retry creating the database schema for the database results backend in case of a race condition (#6298). * When using the Redis results backend, awaiting for a chord no longer hangs when setting :setting:result_expires to 0 (#6373). * When a user tries to specify the app as an option for the subcommand, a custom error message is displayed (#6363). * Fix the --without-gossip, --without-mingle, and --without-heartbeat options which now work as expected. (#6365) * Provide a clearer error message when the application cannot be loaded. * Avoid printing deprecation warnings for settings when they are loaded from Django settings (#6385). * Allow lowercase log levels for the --loglevel option (#6388). * Detaching now works as expected (#6401). * Restore broadcasting messages from celery control (#6400). * Pass back real result for single task chains (#6411). * Ensure group tasks a deeply serialized (#6342). * Fix chord element counting (#6354). * Restore the celery shell command (#6421). * Breaking Change Remove AMQP result backend (#6360). * Warn when deprecated settings are used (#6353). * Expose retry_policy for Redis result backend (#6330). * Prepare Celery to support the yet to be released Python 3.9 (#6328). * More cleanups of leftover Python 2 support (#6338). * Bump minimum required eventlet version to 0.26.1. * Update Couchbase Result backend to use SDK V3. * Restore monkeypatching when gevent or eventlet are used. * Allow to opt out of ordered group results when using the Redis result backend (#6290). * Breaking Change Remove the deprecated celery.utils.encoding module. * Breaking Change Drop support for the Riak result backend (#5686). * Breaking Change pytest plugin is no longer enabled by default (#6288). Install pytest-celery to enable it. * Breaking Change Brand new CLI based on Click (#5718). * Bump Kombu version to 5.0 (#5686). * Removed most of the compatibility code that supports Python 2 (#5686). * Modernized code to work on Python 3.6 and above (#5686). - Update BuildRequires/Requires. - Add patch move-pytest-configuration-to-conftest.patch to fix testsuite.Steve Kowalik2020-11-17 04:19:59 +00:00
b5efc56345- Update to 4.2.1: * Fix to build with newest kombu * Many bugfixes around - Add patch to skip test that should not be run: * celery-no-redis.patch
Tomáš Chvátal
2018-08-16 11:11:59 +00:00
fcdea0f7a7Accepting request 200670 from devel:languages:python
Stephan Kulow
2013-09-27 15:58:53 +00:00
06983cd450Accepting request 200634 from home:posophe:branches:devel:languages:python
Sascha Peilicke
2013-09-26 07:53:51 +00:00
a49f886f2dAccepting request 179748 from devel:languages:python
Stephan Kulow
2013-07-16 05:37:56 +00:00
af5b4dc9a5- Update to 3.0.19: - Now depends on billiard 2.7.3.28 - A Python 3 related fix managed to disable the deadlock fix announced in 3.0.18. Tests have been added to make sure this does not happen again. - Task retry policy: Default max_retries is now 3. This ensures clients will not be hanging while the broker is down. You can set a longer retry for the worker by using the celeryd_after_setup signal: from celery.signals import celeryd_after_setup @celeryd_after_setup.connect def configure_worker(instance, conf, **kwargs): conf.CELERY_TASK_PUBLISH_RETRY_POLICY = { 'max_retries': 100, 'interval_start': 0, 'interval_max': 1, 'interval_step': 0.2, } - Worker: Will now properly display message body in error messages even if the body is a buffer instance. - 3.0.18 broke the MongoDB result backend (Issue #1303).
Alexandre Rogoski
2013-04-30 19:38:27 +00:00
1d9340b693- Update to 3.0.18: - Now depends on kombu 2.5.10. See the kombu changelog. - Now depends on billiard 2.7.3.27. - Can now specify a whitelist of accepted serializers using the new CELERY_ACCEPT_CONTENT setting. This means that you can force the worker to discard messages serialized with pickle and other untrusted serializers. For example to only allow JSON serialized messages use:: CELERY_ACCEPT_CONTENT = ['json'] you can also specify MIME types in the whitelist:: CELERY_ACCEPT_CONTENT = ['application/json'] - Fixed deadlock in multiprocessing's pool caused by the semaphore not being released when terminated by signal. - Processes Pool: It's now possible to debug pool processes using GDB. - celery report now censors possibly secret settings, like passwords and secret tokens. You should still check the output before pasting anything on the internet. - Connection URLs now ignore multiple '+' tokens. - Worker/statedb: Now uses pickle protocol 2 (Py2.5+) - Fixed Python 3 compatibility issues. - Worker: A warning is now given if a worker is started with the same node name as an existing worker. - Worker: Fixed a deadlock that could occur while revoking tasks (Issue #1297). - Worker: The :sig:HUP handler now closes all open file descriptors before restarting to ensure file descriptors does not leak (Issue #1270). - Worker: Optimized storing/loading the revoked tasks list (Issue #1289). After this change the --statedb file will take up more disk space, but loading from and storing the revoked tasks will be considerably
Alexandre Rogoski
2013-04-12 18:08:39 +00:00
a15429bc15- Update to 3.0.16: - Happy International Women's Day! We have a long way to go, so this is a chance for you to get involved in one of the organizations working for making our communities more diverse. - PyLadies — http://pyladies.com - Girls Who Code — http://www.girlswhocode.com - Women Who Code — http://www.meetup.com/Women-Who-Code-SF/ - Now depends on :mod:kombu version 2.5.7 - Now depends on :mod:billiard version 2.7.3.22 - AMQP heartbeats are now disabled by default. Some users experiences issues with heartbeats enabled, and it's not strictly necessary to use them. If you're experiencing problems detecting connection failures, you can re-enable heartbeats by configuring the BROKER_HEARTBEAT setting. - Worker: Now propagates connection errors occurring in multiprocessing callbacks, so that the connection can be reset (Issue #1226). - Worker: Now propagates connection errors occurring in timer callbacks, so that the connection can be reset. - The modules in CELERY_IMPORTS and CELERY_INCLUDE are now imported in the original order (Issue #1161). The modules in CELERY_IMPORTS will be imported first, then continued by CELERY_INCLUDE. Thanks to Joey Wilhelm. - New bash completion for celery available in the git repository: https://github.com/celery/celery/tree/3.0/extra/bash-completion You can source this file or put it in bash_completion.d to get auto-completion for the celery command-line utility. - The node name of a worker can now include unicode characters (Issue #1186).
Alexandre Rogoski
2013-03-08 21:44:57 +00:00
b567dfac31- Update to 3.0.15: - Now depends on billiard 2.7.3.21 which fixed a syntax error crash. - Fixed bug with CELERY_SEND_TASK_SENT_EVENT.
Alexandre Rogoski
2013-02-12 21:45:37 +00:00
f2d8904592- 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
Alexandre Rogoski
2013-02-08 20:24:43 +00:00
f776f7ac60- Update to 3.0.13: - Now depends on Kombu 2.5 - py-amqp has replaced amqplib as the default transport, gaining support for AMQP 0.9, and the RabbitMQ extensions including Consumer Cancel Notifications and heartbeats. - support for multiple connection URLs for failover. - Read more in the Kombu 2.5 changelog. - Now depends on billiard 2.7.3.19 - Fixed a deadlock issue that could occur when the producer pool inherited the connection pool instance of the parent process. - The --loader option now works again (Issue #1066). - celery umbrella command: All subcommands now supports the --workdir option (Issue #1063). - Groups included in chains now give GroupResults (Issue #1057) Previously it would incorrectly add a regular result instead of a group result, but now this works: # [4 + 4, 4 + 8, 16 + 8] >>> res = (add.s(2, 2) | group(add.s(4), add.s(8), add.s(16)))() >>> res <GroupResult: a0acf905-c704-499e-b03a-8d445e6398f7 [ 4346501c-cb99-4ad8-8577-12256c7a22b1, b12ead10-a622-4d44-86e9-3193a778f345, 26c7a420-11f3-4b33-8fac-66cd3b62abfd]> - Chains can now chain other chains and use partial arguments (Issue #1057). Example: >>> c1 = (add.s(2) | add.s(4)) >>> c2 = (add.s(8) | add.s(16)) >>> c3 = (c1 | c2) # 8 + 2 + 4 + 8 + 16 >>> assert c3(8).get() == 38
Alexandre Rogoski
2013-01-07 16:42:46 +00:00
a8371afa35- Update to 3.0.12: - Now depends on kombu 2.4.8 - [Redis] New and improved fair queue cycle algorithm (Kevin McCarthy). - [Redis] Now uses a Redis-based mutex when restoring messages. - [Redis] Number of messages that can be restored in one interval is no longer limited (but can be set using the unacked_restore_limit transport option <BROKER_TRANSPORT_OPTIONS>.) - Heartbeat value can be specified in broker URLs (Mher Movsisyan). - Fixed problem with msgpack on Python 3 (Jasper Bryant-Greene). - Now depends on billiard 2.7.3.18 - Celery can now be used with static analysis tools like PyDev/PyCharm/pylint etc. - Development documentation has moved to Read The Docs. The new URL is: http://docs.celeryproject.org/en/master - New CELERY_QUEUE_HA_POLICY setting used to set the default HA policy for queues when using RabbitMQ. New method Task.subtask_from_request returns a subtask using the current request. - Results get_many method did not respect timeout argument. Fix contributed by Remigiusz Modrzejewski - generic_init.d scripts now support setting CELERY_CREATE_DIRS to always create log and pid directories (Issue #1045). This can be set in your /etc/default/celeryd. - Fixed strange kombu import problem on Python 3.2 (Issue #1034). - Worker: ETA scheduler now uses millisecond precision (Issue #1040). - The --config argument to programs is now supported by all loaders. - The CASSANDRA_OPTIONS setting has now been documented. Contributed by Jared Biel. - Task methods celery.contrib.methods cannot be used with the old
Alexandre Rogoski
2012-11-06 18:12:55 +00:00
767ea655cdAccepting request 137358 from devel:languages:python
Stephan Kulow
2012-10-07 17:55:14 +00:00
eb8e3de37b- Update to 3.0.11: - generic-init.d scripts changed permissions of /var/log & /var/run In the daemonization tutorial the recommended directories were as follows: CELERYD_LOG_FILE="/var/log/celery/%n.log" CELERYD_PID_FILE="/var/run/celery/%n.pid" But in the scripts themselves the default files were /var/log/celery%n.log and /var/run/celery%n.pid, so if the user did not change the location by configuration, the directories /var/log and /var/run would be created - and worse have their permissions and owners changed. This change means that: - Default pid file is /var/run/celery/%n.pid - Default log file is /var/log/celery/%n.log - The directories are only created and have their permissions changed if *no custom locations are set*. Users can force paths to be created by calling the create-paths subcommand: $ sudo /etc/init.d/celeryd create-paths Upgrading Celery will not update init scripts To update the init scripts you have to re-download the files from source control and update them manually. You can find the init scripts for version 3.0.x at: http://github.com/celery/celery/tree/3.0/extra/generic-init.d - Now depends on billiard 2.7.3.17 - Fixes request stack protection when app is initialized more than once (Issue #1003). - ETA tasks now properly works when system timezone is not the same as the configured timezone (Issue #1004). - Terminating a task now works if the task has been sent to the pool but not yet acknowledged by a pool process (Issue #1007). Fix contributed by Alexey Zatelepin
Alexandre Rogoski
2012-09-26 18:10:11 +00:00
22fb34fcd6- Update to 3.0.10: - Now depends on kombu 2.4.7 - Now depends on billiard 2.7.3.14 - Fixes crash at startup when using Django and pre-1.4 projects (setup_environ). - Hard time limits now sends the KILL signal shortly after TERM, to terminate processes that have signal handlers blocked by C extensions. - Billiard now installs even if the C extension cannot be built. It's still recommended to build the C extension if you are using a transport other than rabbitmq/redis (or use forced execv for some other reason). - Pool now sets a `current_process().index` attribute that can be used to create as many log files as there are processes in the pool. - Canvas: chord/group/chain no longer modifies the state when called Previously calling a chord/group/chain would modify the ids of subtasks so that: >>> c = chord([add.s(2, 2), add.s(4, 4)], xsum.s()) >>> c() >>> c() <-- call again at the second time the ids for the tasks would be the same as in the previous invocation. This is now fixed, so that calling a subtask won't mutate any options. - Canvas: Chaining a chord to another task now works (Issue #965). - Worker: Fixed a bug where the request stack could be corrupted if relative imports are used. Problem usually manifested itself as an exception while trying to send a failed task result (NoneType does not have id attribute). Fix contributed by Sam Cooke. - Tasks can now raise celery.exceptions.Ignore to skip updating states or events after return.
Alexandre Rogoski
2012-09-20 22:32:14 +00:00
d38f45e780Accepting request 134036 from devel:languages:python
Ismail Dönmez
2012-09-14 10:34:26 +00:00
95c82d7a10- Update to 3.0.9: - Important note for users of Django and the database scheduler! Recently a timezone issue has been fixed for periodic tasks, but erroneous timezones could have already been stored in the database, so for the fix to work you need to reset the last_run_at fields. You can do this by executing the following command: $ python manage.py shell >>> from djcelery.models import PeriodicTask >>> PeriodicTask.objects.update(last_run_at=None) You also have to do this if you change the timezone or CELERY_ENABLE_UTC setting. - Note about the CELERY_ENABLE_UTC setting. If you previously disabled this just to force periodic tasks to work with your timezone, then you are now *encouraged to re-enable it*. - Now depends on Kombu 2.4.5 which fixes PyPy + Jython installation. - Fixed bug with timezones when :setting:CELERY_ENABLE_UTC is disabled (Issue #952). - Fixed a typo in the celerybeat upgrade mechanism (Issue #951). - Make sure the exc_info argument to logging is resolved (Issue #899). - Fixed problem with Python 3.2 and thread join timeout overflow (Issue #796). - A test case was occasionally broken for Python 2.5. - Unit test suite now passes for PyPy 1.9. - App instances now supports the with statement. This calls the new :meth:~celery.Celery.close method at exit, which cleans up after the app like closing pool connections. Note that this is only necessary when dynamically creating apps, e.g. for "temporary" apps. - Support for piping a subtask to a chain. For example:
Alexandre Rogoski
2012-08-31 23:50:10 +00:00
5130ed949d- Update to 3.0.8: - Now depends on Kombu 2.4.4 - Beat: Fixed another timezone bug with interval and crontab schedules (Issue #943). - Beat: The schedule file is now automatically cleared if the timezone is changed. The schedule is also cleared when you upgrade to 3.0.8 from an earlier version, this to register the initial timezone info. - Events: The worker-heartbeat event now include processed and active count fields. Contributed by Mher Movsisyan. - Fixed error with error email and new task classes (Issue #931). - BaseTask.__call__ is no longer optimized away if it has been monkey patched. - Fixed shutdown issue when using gevent (Issue #911 & Issue #936). Fix contributed by Thomas Meson.
Alexandre Rogoski
2012-08-29 18:17:50 +00:00
510815b44a- Update to 3.0.7: - Fixes several problems with periodic tasks and timezones (Issue #937). - Now depends on kombu 2.4.2 - Redis: Fixes a race condition crash - Fixes an infinite loop that could happen when retrying establishing the broker connection. - Daemons now redirect standard file descriptors to /dev/null Though by default the standard outs are also redirected to the logger instead, but you can disable this by changing the CELERY_REDIRECT_STDOUTS setting. - Fixes possible problems when eventlet/gevent is patched too late. - LoggingProxy no longer defines fileno() (Issue #928). - Results are now ignored for the chord unlock task. Fix contributed by Steeve Morin. - Cassandra backend now works if result expiry is disabled. Fix contributed by Steeve Morin. - The traceback object is now passed to signal handlers instead of the string representation. Fix contributed by Adam DePue. - Celery command: Extensions are now sorted by name. - A regression caused the task-failed event to be sent with the exception object instead of its string representation. - The worker daemon would try to create the pid file before daemonizing to catch errors, but this file was not immediately released (Issue #923). - Fixes Jython compatibility. - billiard.forking_enable was called by all pools not just the processes pool, which would result in a useless warning if the billiard C extensions were not installed.
Alexandre Rogoski
2012-08-24 22:34:37 +00:00
c1a4420793- Update to 3.0.6: - Now depends on kombu 2.4.0 - Now depends on billiard 2.7.3.12 - Redis: Celery now tries to restore messages whenever there are no messages in the queue. - Crontab schedules now properly respects CELERY_TIMEZONE setting. It's important to note that crontab schedules uses UTC time by default unless this setting is set. Issue #904 and django-celery #150. - billiard.enable_forking is now only set by the processes pool. - The transport is now properly shown by celery report (Issue #913). - The --app argument now works if the last part is a module name (Issue #921). - Fixed problem with unpickleable exceptions (billiard #12). - Adds task_name attribute to EagerResult which is always None (Issue #907). - Old Task class in celery.task no longer accepts magic kwargs by default (Issue #918). A regression long ago disabled magic kwargs for these, and since no one has complained about it we don't have any incentive to fix it now. - The inspect reserved control command did not work properly. - Should now play better with static analyzation tools by explicitly specifying dynamically created attributes in the celery and celery.task modules. - Terminating a task now results in celery.exceptions.RevokedTaskError instead of a WorkerLostError. - AsyncResult.revoke now accepts terminate and signal arguments. - The task-revoked event now includes new fields: terminated, signum, and expired.
Alexandre Rogoski
2012-08-17 22:42:05 +00:00
0166a5212b- Update to 3.0.5: - Now depends on kombu 2.3.1 + billiard 2.7.3.11 - Fixed a bug with the -B option (`cannot pickle thread.lock objects`) (Issue #894 + Issue #892, + django-celery #154). - The restart_pool control command now requires the CELERYD_POOL_RESTARTS setting to be enabled This change was necessary as the multiprocessing event that the restart command depends on is responsible for creating many semaphores/file descriptors, resulting in problems in some environments. - chain.apply now passes args to the first task (Issue #889). - Documented previously secret options to the Django-Celery monitor in the monitoring userguide (Issue #396). - Old changelog are now organized in separate documents for each series, history.
Alexandre Rogoski
2012-08-01 19:14:57 +00:00
49f102c913- Update to 3.0.4: - Now depends on Kombu 2.3 - New experimental standalone Celery monitor: Flower See monitoring-flower to read more about it! Contributed by Mher Movsisyan. - Now supports AMQP heartbeats if using the new pyamqp:// transport. - The py-amqp transport requires the amqp library to be installed: $ pip install amqp - Then you need to set the transport URL prefix to pyamqp://. - The default heartbeat value is 10 seconds, but this can be changed using the BROKER_HEARTBEAT setting BROKER_HEARTBEAT = 5.0 - If the broker heartbeat is set to 10 seconds, the heartbeats will be monitored every 5 seconds (double the hertbeat rate). See the Kombu 2.3 changelog for more information. - Now supports RabbitMQ Consumer Cancel Notifications, using the pyamqp:// transport. This is essential when running RabbitMQ in a cluster. See the Kombu 2.3 changelog for more information. - Delivery info is no longer passed directly through. It was discovered that the SQS transport adds objects that can't be pickled to the delivery info mapping, so we had to go back to using the whitelist again. Fixing this bug also means that the SQS transport is now working again. - The semaphore was not properly released when a task was revoked (Issue #877). This could lead to tasks being swallowed and not released until a worker restart. Thanks to Hynek Schlawack for debugging the issue. - Retrying a task now also forwards any linked tasks. This means that if a task is part of a chain (or linked in some other
Alexandre Rogoski
2012-07-26 22:25:25 +00:00
88a91c8ca2- Update to 3.0.3: - amqplib passes the channel object as part of the delivery_info and it's not pickleable, so we now remove it.
Alexandre Rogoski
2012-07-20 21:17:03 +00:00