river
river copied to clipboard
riverqueue
Fast and reliable background jobs in Go
There are a few places in the River code which use `context.Background()` to bypass potential cancellation, like this: ```go func (p *producer) dispatchWork(count int, fetchResultCh chan
This one popped up in CI tonight: https://github.com/riverqueue/river/actions/runs/10224466966/job/28292226269 Haven’t dug into it yet but making sure we can track it.
the insert only clients fail to rescue jobs, because https://github.com/riverqueue/river/blob/master/internal/maintenance/job_rescuer.go#L272-L277 it seems it looks to see if there are jobs registered, but since insert only clients have no workers configured,...
I was looking into why River's example tests were so incredibly slow. By far the biggest reason was that maintenance services were jittering on start up, but by far the...
We have a use-case where we need to add queues dynamically. The description of the use-case: we have multiple `Kind` of jobs, and one particular is the `manage_rewards`. This `Kind`...
We do have ByArgs argument in UniqueOpts but unfortunately it is not good enough for my use case to describe uniqueness of the job (because I have different timestamps, requests...
This is a rebased version of #584 that's been adapted for recent changes including consolidated insert logic and the newer unique jobs implementation.
When using the `errros.Join` to return a result from a `Work` function, all errors are recorded as a single string in the database, which can be inconvenient when viewing a...
Hi! I am using the example `SortWorker` job with small adjustments to test longer-running jobs with cancellation but it does not seem to work. ```go const SortJobKind = "sort" type...
Here, experiment with a middleware-like system that adds middleware functions to job lifecycles, which results in them being invoked during specific phases of a job like as it's being inserted...