river icon indicating copy to clipboard operation
river copied to clipboard

Fast and reliable background jobs in Go

Results 96 river issues
Sort by recently updated
recently updated
newest added

Right now `JobListParams.Metadata()` only offers querying via `metadata >@ …`, but I'd like to do slightly more advanced stuff. For example if the metadata contains: {"object_id": 42} And I'd like...

**Problem** [JobCleaner runOnce has a strict deadline which 30*time.Second](https://github.com/riverqueue/river/blob/8669cbc38baf69eeda9dc4eb2944e8ef514d12c7/internal/maintenance/job_cleaner.go#L150), that would be nice to set it dynamically. **Reason** We got a bigger load in our queue, which was 15.000.000 job...

I would like to see logs emitted by a job in a pane in the UI alongside the errors and so on. I think this could be implemented by storing...

A repo demonstrating the issue is available here: https://github.com/wydengyre/dbsqlintervaldemo Using `riverdatabasesql` with the `pq` driver will result in failure of the leader election system. The leader election SQL will result...

I wonder if this feature is on your roadmap. TL;DR; Job aggregation allows you to enqueue multiple jobs successively, and have them passed to the Worker together rather than individually....

enhancement

Here, add a new complimentary pair for `HookWorkBegin`: `HookWorkEnd`, which runs after workers finish, taking in an error result. `HookWorkEnd` hooks may or may not modify the error result, choosing...

Try to fix one of the most commonly failing intermittent tests we have left, which is the stress test in the notifier [1]. --- FAIL: TestNotifier (0.00s) --- FAIL: TestNotifier/MultipleSubscribersStress...

Fix a series of tests in `Test_Client_JobCompletion` that may fail [1] intermittently due to their use of a real world clock that may be off as test goroutines are paused...

Fix another failing intermittent test [1] that has timing constraints that are in practice just too tight for slower environments like GitHub Actions CI where there might be a lot...

There's a bunch of clock-based testing happening in the leader tests for drivers, resulting in intermittent failures like this one [1]: --- FAIL: TestDriverRiverPgxV5 (23.18s) driver_test.go:73: Reusing idle schema "river_2025_04_26t17_52_50_schema_07"...