Changelog History
Page 4
-
v1.5.4 Changes
- Implemented atomic "set if not exists" for Redis and SQLite, which is used by the locking APIs.
-
v1.5.3 Changes
- Includes addition of
TaskLockandHuey.lock_task()helpers. - Extend
HueyAPI to add method for creating the consumer.
- Includes addition of
-
v1.5.2 Changes
- ➕ Added support for gracefully restarting the consumer using SIGHUP.
- 🛠 Fixed a bug where periodic tasks were not being given unique task IDs when executed by the consumer. Periodic tasks now receive a unique ID each time they are invoked.
-
v1.5.1 Changes
➕ Added support for specifying a
retryandretry_delayon periodic tasks. Simply pass the desired values into theperiodic_task()decorator after the validation function, as keyword arguments. -
v1.5.0 Changes
- 👍 Allow all instances of a task to be revoked/restored by adding the
revoke(),restore()andis_revoked()methods to all decorated tasks (where previously they were only available on periodic tasks). - Periodic task instances now have a unique identifier.
- ➕ Added documentation on how to correctly use the Django consumer management
command with the
geventworker model. - 🌲 Logging will lazily resolve log messages.
- 🐛 Bug was fixed that prevented the local (non-global) task registry from working as intended. This is now fixed.
- 📄 Docstrings added to the
BaseStorageAPIs.
Thanks to @mindojo-victor and @nachtmaar for help with some of the above items.
- 👍 Allow all instances of a task to be revoked/restored by adding the
-
v1.4.1 Changes
- Support using
7to represent Sunday when doing day-of-week calculations in thecrontabhelper. - 🛠 Fix bug #243, wherein Django interpreted boolean CLI arguments as having a boolean default value.
- Support using
-
v1.4.0 Changes
🛠 Fixed a subtle bug in the way Huey calculated when to run the periodic task ⏱ scheduler. If you had configured the consumer to check the schedule at an interval that was not a factor of 60, then there is a chance that periodic ⏱ tasks may be scheduled at incorrect intervals from one minute to the next. This 🛠 is fixed in 1.4.0.
➕ Added better signal handling in order to support graceful shutdown. Graceful 👷 shutdown involves letting workers finish executing any tasks they may be 🚦 processing at the time the shutdown signal is received. The default behavior is 👷 to interrupt the workers mid-task. Huey uses
SIGTERMto shutdown the consumer immediately, andSIGINTto gracefully shutdown.➕ Added support for using either a global task registry, or a registry bound to 0️⃣ a particular
Hueyinstance. The default behavior is to use a global registry (backwards-compatible). To bind the registry to a singleHueyinstance, passglobal_registry=Falsewhen initializing yourHueyobject.➕ Added a
reschedule()method to theTaskResultWrapper.📚 Documentation clean-ups and additions, particularly around the logic used to 📄 handle datetime conversion. Also added docs on shutdown modes for huey consumer.
-
v1.3.1 Changes
Smarter conversion between datetimes, so that huey will correctly interpret 🔧 naive or timezone-aware datetimes and properly convert to UTC when configured to do so. Previously, huey only operated on naive datetimes. Many thanks to @Antoine for this patch-set.
📚 Documentation clean-ups and additions.
-
v1.3.0 Changes
➕ Adds flag to preserve result-store value in certain circumstances. Contains yet 🔧 more hacking at the consumer configuration options, specifically hard-coded 🚚 defaults are removed from the option definitions.
👍 The
run_hueymanagement command was simplified as we are dropping support for 👍 older (officially unsupported) versions of Django.➕ Added a
sqlitedbcontrib module that uses a local SQLite database instead of ⏱ Redis for Queue persistence, task scheduling and result-storage. -
v1.2.3 Changes
Contains an attempt at fixing the django management command handling of the 0️⃣
defaultoption.