Next | Query returned 3 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2019-01-07 13:59:36 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-django-celery-beat: updated to 1.4.0

1.4.0:
- Fix migrations dependencies.
- Added the DJANGO_CELERY_BEAT_TZ_AWARE setting.

1.3.0:
- Fix transaction handling while syncing the schedule.
- Fix schedule type validation logic.
- Scheduler no longer forgets the tasks after first schedule change.
- Fix race condition for schedule_changed() resulting in erroneously closed \ 
connections.
- Add support for task priorities when using RabbitMQ or Redis as broker.
- Disabled tasks are now correctly deleted from the schedule.
- Added name as search filter.

1.2.0:
- Allow timezone-aware Cron schedules.
- Retry later in case of InterfaceError in sync.
- Show Periodic Task Description in panel admin.
- Fix CrontabSchedule example.
- Support Periodic Tasks with a start date and one-off tasks.
- Fixes a problem with beat not reconnecting to MySQL (server restart, network \ 
problem, etc.) when checking if schedule has changed.
- Add toggle admin action which allows to activate disabled tasks or deactivate \ 
enabled tasks.
- Add fields validation for CrontabSchedule.
- Drop support for Django<1.11.
- Fix task heap invalidation bug which prevented scheduled tasks from running \ 
when syncing tasks from the database.
- Raise a ValidationError when more than one type (solar, crontab or interval) \ 
of schedule is provided.
   2018-02-22 11:30:38 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-django-celery-beat: updated to 1.1.1

1.1.1
- Fix interval schedules by providing nowfun.
- Removing code that forced last_run_at to be timezone naive for no reason, made \ 
timezone aware. Fixes crontab schedules
- Entry.last_run_at is no-longer timezone naive.
- Use a localized PyTZ timezone object for now() otherwise conversions fail \ 
scheduling breaks resulting in constant running of tasks or possibly not running \ 
ever.
- Fix endless migrations creation for solar schedules events.
- Prevent MySQL has gone away errors.
- Added support for Django 2.0.
- Adjust CrontabSchedule's minutes, hour & day_of_month fields max length
   2018-01-11 15:35:40 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
py-django-celery-beat: added version 1.1.0

This extension enables you to store the periodic task schedule in the database.

The periodic tasks can be managed from the Django Admin interface, where you
can create, edit and delete periodic tasks and how often they should run.

Next | Query returned 3 messages, browsing 1 to 10 | previous