Bump rq from 0.12.0 to 1.2.2 in /app

[dependabot-preview[bot]]

Bumps rq from 0.12.0 to 1.2.2.

Release notes

Sourced from rq's releases.

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.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 in place of the deprecated 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!

Changelog

Sourced from rq's changelog.

RQ 1.2.2 (2020-01-31)

• Job.fetch() now properly handles unpickleable return values. Thanks @selwin!

RQ 1.2.1 (2020-01-31)

• 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!

RQ 1.2.0 (2020-01-04)

• 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!

RQ 1.1.0 (2019-07-20)

• 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 (2019-04-06)

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 in place of the deprecated Raven library
  • RQ will look for the more explicit RQ_SENTRY_DSN environment variable instead of SENTRY_DSN before instantiating Sentry integration
  • Thanks @selwin!

... (truncated)

Commits

• f18a951 Bump version to 1.2.2
• fda4b35 Fixes Job.fetch when return value is unpickleable (#1184)
• 90e032c Bump version to 1.2.1
• ed67de2 Add job status setting in enqueue_at (and in enqueue_in) methods (#1181)
• ccfd4a0 Failed jobs will now auto expire (#1182)
• 927fb5a Bump version to 1.2.0
• 5f949f4 Add a hard kill from the parent process with a 10% increased timeout … (#1169)
• 37a6304 fix: use correct logging handler for scheduler (#1178)
• baa0cc2 Job scheduling (#1163)
• f09d4db Travis CI: sudo: deprecated and Xenial is default (#1175)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)