Kristian Desjardins

I'm pretty sure this was fixed after 1.3.6 in: Bug #4319: Treat EINTR like EAGAIN https://github.com/proftpd/proftpd/commit/f09f0c661621eb22cb1ce579194478007ba62866 I was having the same issue until I built proftpd with a version between...

> translate from frontend FTP to backend SFTP (not sure where this might be useful, though?) Our use case would be to support using an SFTP backend with a legacy...

Forward, in my case.

Problem with TERM=ansi is that mouse mode does not work.

Ok thanks. I do like the new Request struct layout as I was doing this myself in my own struct. Overall, it's much simpler now.

Ok, if I add the storage via .data, then I get: Worker missing required context: Missing the an entry for `apalis_core::task::task_id::TaskId`. Did you forget to add `.data()

Creating the worker pool: ```rust let storage: PostgresStorage = PostgresStorage::new(pool.clone()); let worker = WorkerBuilder::new("MyWorker") .chain(|srv| srv.layer(TraceLayer::new())) .backend(storage.clone()) .build_fn(execute); ``` The build_fn like the fn-args example: ```rust pub async fn execute(...

With that setup I get many trait errors like: 72 | .build_fn(execute); | ^^^^^^^^ the trait `Service` is not implemented for `ServiceFn impl Future {execute}, MyReq, SqlContext, _>`, which is...

Compiles and runs, but now the job gets stuck in the running state.

Is this related to https://github.com/geofmureithi/apalis/discussions/422 ? My build_fn finishes fine, and I see job.done: DEBUG ThreadId(06) task: apalis::layers::tracing::on_response: job.done done_in=1ms result=OverallResult { ... } but the status does not change...