-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Worker never ends if I use kable in it #567
Comments
I have the most recent version 0.27.0 |
This is likely a duplicate of #378. I've been slowly integrating changes in Kable to address the issue, it will be some time before it can be completely fixed. In the mean time, one possible workaround is to create a parent override suspend fun doWork(): Result = withContext(Dispatchers.IO) {
val scope = CoroutineScope(Job(coroutineContext.job))
try {
val peripheral = scope.peripheral(..)
} finally {
scope.cancel()
}
} |
I'm hoping to get changes into 0.29.0 that would remove the need for this workaround. |
Unfortunately lots of other things came up and this didn't happen. I'll try to get back to this when I can, but being that there is a workaround, it might not get prioritized very high vs. some other bugs. Thanks for being patient! |
If I just create a
periferal
instance inside worker then this worker never ends.I am enqueueing a unique work. For the first time it runs fine (I see in logs
Finished worker
), when I enqueue again the work it does not start. I assume this is because the previous work was not finished.The text was updated successfully, but these errors were encountered: