Skip to content

Update rq to 1.2.2#534

Closed
pyup-bot wants to merge 1 commit intomasterfrom
pyup-update-rq-0.12.0-to-1.2.2
Closed

Update rq to 1.2.2#534
pyup-bot wants to merge 1 commit intomasterfrom
pyup-update-rq-0.12.0-to-1.2.2

Conversation

@pyup-bot
Copy link
Copy Markdown
Collaborator

This PR updates rq from 0.12.0 to 1.2.2.

Changelog

1.2.2

* `Job.fetch()` now properly handles unpickleable return values. Thanks selwin!

1.2.1

* `enqueue_at()` and `enqueue_in()` now sets job status to `scheduled`. Thanks coolhacker170597!
* Failed jobs data are now automatically expired by Redis. Thanks selwin!
* Fixes `RQScheduler` logging configuration. Thanks FlorianPerucki!

1.2.0

* This release also contains an alpha version of RQ's builtin job scheduling mechanism. Thanks selwin!
* Various internal API changes in preparation to support multiple job dependencies. Thanks thomasmatecki!
* `--verbose` or `--quiet` CLI arguments should override `--logging-level`. Thanks zyt312074545!
* Fixes a bug in `rq info` where it doesn't show workers for empty queues. Thanks zyt312074545!
* Fixed `queue.enqueue_dependents()` on custom `Queue` classes. Thanks van-ess0!
* `RQ` and Python versions are now stored in job metadata. Thanks eoranged!
* Added `failure_ttl` argument to job decorator. Thanks pax0r!

1.1.0

- Added `max_jobs` to `Worker.work` and `--max-jobs` to `rq worker` CLI. Thanks perobertson!
- Passing `--disable-job-desc-logging` to `rq worker` now does what it's supposed to do. Thanks janierdavila!
- `StartedJobRegistry` now properly handles jobs with infinite timeout. Thanks macintoshpie!
- `rq info` CLI command now cleans up registries when it first runs. Thanks selwin!
- Replaced the use of `procname` with `setproctitle`. Thanks j178!

1.0

Backward incompatible changes:

- `job.status` has been removed. Use `job.get_status()` and `job.set_status()` instead. Thanks selwin!

- `FailedQueue` has been replaced with `FailedJobRegistry`:
* `get_failed_queue()` function has been removed. Please use `FailedJobRegistry(queue=queue)` instead.
* `move_to_failed_queue()` has been removed.
* RQ now provides a mechanism to automatically cleanup failed jobs. By default, failed jobs are kept for 1 year.
* Thanks selwin!

- RQ's custom job exception handling mechanism has also changed slightly:
* RQ's default exception handling mechanism (moving jobs to `FailedJobRegistry`) can be disabled by doing `Worker(disable_default_exception_handler=True)`.
* Custom exception handlers are no longer executed in reverse order.
* Thanks selwin!

- `Worker` names are now randomized. Thanks selwin!

- `timeout` argument on `queue.enqueue()` has been deprecated in favor of `job_timeout`. Thanks selwin!

- Sentry integration has been reworked:
* RQ now uses the new [sentry-sdk](https://pypi.org/project/sentry-sdk/) in place of the deprecated [Raven](https://pypi.org/project/raven/) library
* RQ will look for the more explicit `RQ_SENTRY_DSN` environment variable instead of `SENTRY_DSN` before instantiating Sentry integration
* Thanks selwin!

- Fixed `Worker.total_working_time` accounting bug. Thanks selwin!

0.13.0

- Compatibility with Redis 3.0. Thanks dash-rai!
- Added `job_timeout` argument to `queue.enqueue()`. This argument will eventually replace `timeout` argument. Thanks selwin!
- Added `job_id` argument to `BaseDeathPenalty` class. Thanks loopbio!
- Fixed a bug which causes long running jobs to timeout under `SimpleWorker`. Thanks selwin!
- You can now override worker's name from config file. Thanks houqp!
- Horses will now return exit code 1 if they don't terminate properly (e.g when Redis connection is lost). Thanks selwin!
- Added `date_format` and `log_format` arguments to `Worker` and `rq worker` CLI. Thanks shikharsg!
Links

@pyup-bot pyup-bot mentioned this pull request Jan 31, 2020
@pyup-bot
Copy link
Copy Markdown
Collaborator Author

pyup-bot commented Mar 9, 2020

Closing this in favor of #545

@pyup-bot pyup-bot closed this Mar 9, 2020
@ednilson ednilson deleted the pyup-update-rq-0.12.0-to-1.2.2 branch March 9, 2020 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant