Geoffrey Mureithi comments

Results 63 comments of


                                            Geoffrey Mureithi

Using `deadpool_redis::Pool` with `apalis::redis::RedisStorage`

Thanks, this seems doable. It would need some changes to the calling of commands. We can add this to 0.6.0

Using `deadpool_redis::Pool` with `apalis::redis::RedisStorage`

This has been resolved in 0.6

Dependencies issue

This is noted, and I will look into it. This is not expected behaviour. Possibly because of `tokio-comp`

Dependencies issue

I can confirm that this is caused by including `tokio-comp`. This is a priority issue. > Before 0.5.0 a trick was to use apalis-core & apalis-redis instead of apalis. but...

Dependencies issue

Resolved by https://github.com/geofmureithi/apalis/pull/357

When returning an error from a job, 'last_error' is not set and 'status' is in Done

Currently the functionality is not implemented implicitly (I can add that in 0.5). To do what you need. Consider using a custom Layer and calling `update_with_id`.

When returning an error from a job, 'last_error' is not set and 'status' is in Done

I encourage you to look at https://github.com/geofmureithi/apalis/blob/master/packages/apalis-core/src/layers/ack/mod.rs Ideally you would want to: 1. Create a Retry trait 2. Create a `RetryLayer` which would take in a type that implements `Retry`...

When returning an error from a job, 'last_error' is not set and 'status' is in Done

To be honest, we might be just needing a combination of Ack and Retry in the same layer.

When returning an error from a job, 'last_error' is not set and 'status' is in Done

https://github.com/geofmureithi/apalis/discussions/215#discussioncomment-7774965 Also applies here.