Riverqueue

Latest version: v0.7.0

Safety actively analyzes 682244 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 8

0.0.20

Added

- Added an `ID` setting to the `Client` `Config` type to allow users to override client IDs with their own naming convention. Expose the client ID programatically (in case it's generated) in a new `Client.ID()` method. [PR 206](https://github.com/riverqueue/river/pull/206).

Fixed

- Fix a leadership re-election query bug that would cause past leaders to think they were continuing to win elections. [PR 199](https://github.com/riverqueue/river/pull/199).

0.0.19

Added

- Added `JobGet` and `JobGetTx` to the `Client` to enable easily fetching a single job row from code for introspection. [PR 186].
- Added `JobRetry` and `JobRetryTx` to the `Client` to enable a job to be retried immediately, even if it has already completed, been cancelled, or been discarded. [PR 190].

Changed

- Validate queue name on job insertion. Allow queue names with hyphen separators in addition to underscore. [PR 184](https://github.com/riverqueue/river/pull/184).

0.0.18

Fixed

- Remove a debug statement from periodic job enqueuer that was accidentally left in. [PR 176](https://github.com/riverqueue/river/pull/176).

0.0.17

Added

- Added `JobCancel` and `JobCancelTx` to the `Client` to enable cancellation of jobs. [PR 141](https://github.com/riverqueue/river/pull/141) and [PR #152](https://github.com/riverqueue/river/pull/152).
- Added `ClientFromContext` and `ClientWithContextSafely` helpers to extract the `Client` from the worker's context where it is now available to workers. This simplifies making the River client available within your workers for i.e. enqueueing additional jobs. [PR 145](https://github.com/riverqueue/river/pull/145).
- Add `JobList` API for listing jobs. [PR 117](https://github.com/riverqueue/river/pull/117).
- Added `river validate` command which fails with a non-zero exit code unless all migrations are applied. [PR 170](https://github.com/riverqueue/river/pull/170).

Changed

- For short `JobSnooze` times (smaller than the scheduler's run interval) put the job straight into an `available` state with the specified `scheduled_at` time. This avoids an artificially long delay waiting for the next scheduler run. [PR 162](https://github.com/riverqueue/river/pull/162).

Fixed

- Fixed incorrect default value handling for `ScheduledAt` option with `InsertMany` / `InsertManyTx`. [PR 149](https://github.com/riverqueue/river/pull/149).
- Add missing `t.Helper()` calls in `rivertest` internal functions that caused it to report itself as the site of a test failure. [PR 151](https://github.com/riverqueue/river/pull/151).
- Fixed problem where job uniqueness wasn't being respected when used in conjuction with periodic jobs. [PR 168](https://github.com/riverqueue/river/pull/168).

0.0.16

Changed

- Calls to `Stop` error if the client hasn't been started yet. [PR 138](https://github.com/riverqueue/river/pull/138).

Fixed

- Fix typo in leadership resignation query to ensure faster new leader takeover. [PR 134](https://github.com/riverqueue/river/pull/134).
- Elector now uses the same `log/slog` instance configured by its parent client. [PR 137](https://github.com/riverqueue/river/pull/137).
- Notifier now uses the same `log/slog` instance configured by its parent client. [PR 140](https://github.com/riverqueue/river/pull/140).

0.0.15

Fixed

- Ensure `ScheduledAt` is respected on `InsertManyTx`. [PR 121](https://github.com/riverqueue/river/pull/121).

Page 5 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.