You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@SanjoDeundiak Thanks! Finally got the time to take a look.
If I understand correctly the error in processor or worker initialize function error is just logged by WorkerRelay.
#[cfg_attr(not(feature = "std"), allow(unused_mut))]#[cfg_attr(not(feature = "std"), allow(unused_variables))]asyncfn run(mutself,mutctrl_rx:SmallReceiver<CtrlSignal>){matchself.worker.initialize(&mutself.ctx).await{Ok(()) => {}Err(e) => {error!("Failure during '{}' worker initialisation: {}",
self.ctx.address(),
e
);}}
If I understood correctly this does not stop the worker, but just logs the error. The proposed solution would be to move on to the worker shutdown and context stop ack, without starting the loop in between:
Observed behavior
Currently, if Worker or Processor return an error from its
initialize
function, it's not shut down.Steps to reproduce
Create a dummy Worker that always fails during initialization.
Desired behavior
Worker/Processor should be stopped
Ockam Version
0.116.0
The text was updated successfully, but these errors were encountered: