go-workers
go-workers copied to clipboard
jrallison
Sidekiq compatible background workers in golang
@jrallison you've done an amazing job with this project. [We](https://feeder.co) rely on it a lot for our infrastructure and it works amazingly. We do around 20,000 jobs per minute on...
### Version of go-workers `v0.0.0-20180112190529-dbf81d0b75bb` ### Details - line.86 in workers.fetcher.go - line.81 in workers.enqueue.go  ### My concern I don't know the spec of Sidekiq, but I suspect we...
Hey! First of all, thanks for this amazing package. Have used it a lot at my job and on personal projects and runs awesome. My question is if support for...
The Job func without returning a error value, so how to judge whether a job is success and should retry? Is panic in Job func indicates failed and should retry?
This PR adds some improvements to the retry middleware implemented. 1. Allow configuring retry exponential backoff by using `RetryOptions` struct in `EnqueueOptions` 2. Add `RetryMax` field: even though `Retry` can...
Fixes https://github.com/jrallison/go-workers/issues/68 --- This change is [](https://reviewable.io/reviews/jrallison/go-workers/86)
For example so that we can use Redis over a TLS connection, and that configuration requires more than just strings in a map. This PR also updates `github.com/garyburd/redigo/redis` to `github.com/gomodule/redigo/redis`,...
We pass Sidekiq jobs through `go-workers` to our Rails app. Which works fine for vanilla Sidekiq workers. However when we pair Sidekiq with ActiveJob we get the following error on...
Since JobFunc is part of the function signature of public functions, it should also be public
