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
Currently, the following code is in the runner for services:
// ! temp - enable catching errors in the __initializeService// ! hook. This is only temporary because the "terminate()" function// ! doesn't actually do anything. Eventually, closing a service should// ! be done with message passing for more flexibility.constinitErrHandler=async(body: WorkerBaseMessageBody)=>{if(body.type!==WorkerMessageType.WorkerException)return;awaitexceptionHandler?.({error: (bodyasWorkerExceptionMessageBody).data,terminate: ()=>{//},});};
The terminate() functionality is completely empty, but when this function is called, the worker should be terminated. The Service instance isn't created yet though, so service.close() cannot be called (Service is only initialized one the worker has notified that it is ready). The solution is to use message-passing in order to command the worker at a lower level (lower than Service level).
The text was updated successfully, but these errors were encountered:
Currently, the following code is in the runner for services:
The
terminate()
functionality is completely empty, but when this function is called, the worker should be terminated. TheService
instance isn't created yet though, soservice.close()
cannot be called (Service
is only initialized one the worker has notified that it is ready). The solution is to use message-passing in order to command the worker at a lower level (lower thanService
level).The text was updated successfully, but these errors were encountered: