Yeah

It should work as long as I don't try to serialise coroutine's while they're running...

that would take a feat of engineering

bad engineering

Having said that, we are planning to improve the way that various serialization classes interact with serialization frameworks. One move that I think would help a lot, is that we’ll internally define all the constants like

COROUTINE_SUSPENDED

via internal enum class. Java enums are typically recognized by serialization frameworks and that would reduce the need for doing those kind of hacks that you did.

In my code, I have an ArrayBroadcastChannel that sends strings to two subscribers: Only the first subscriber processes the strings. No chart or snackbar are displayed at the end of the stream of strings. I've searched and read the Kotlin Coroutines guides, but I don't get how to solve this problem. Any help is much appreciated.

@restioson There is no way to serialize a running coroutine. You’ll have to have a JVM that supports serialization of a running thread (there were/are some research ones that were trying to do it, but)

Yeah, I don't intend to try haha

@User uploaded a file: UI not uptated

Thanks so much for your help, @elizarov!

@alucard The most likely explanation is that the first coroutine you launch finishes reading all the data before the consumers are even started. Note, that

BroadcastChannel

is transmitting sent items only to consumers that were already there at the time when the

send

if invoked. You need to

open

all the subscriptions you need first, then start sending the data to the broadcast channel if you want to get it all.

Thank you, @elizarov. The consumers are already opened when the BroadcastChannel starts to send data.

Because most of the time the funcion readLine() retuns null when there is no data over the serial

@alucard Can you reproduce it with some self-contained example? Replacing serial data with some random data generator, for example?

I've tested it with an int list and using println in the consumeEach. It worked. But when I try to use the same pattern on my Android app (get data, do some processing, and then display a dot in a chart), only the first consumeEach seems to work

@elizarov hmm, it does not persist over runs of the application

It deserialises, but does not run when resumed

I've run it once with

start

and then again with

deser

@alucard In the code that you’ve shown you first consume all items that match

isNumber

, then consume all items that

isSampleMessage

. You should never do anything in the second

consumeEach

invocation — getting there would mean the channel is already closed.

it's basically the same code, but across runs of the proc

hm, actually on the second run it exits the program and does execute the

while

loop

Odd

after deserialiseCoro has been called, the program just exits

@User uploaded a file: Untitled

It doesn't seem like the function is doing anything weird

Looks like an exception is thrown and propagates to a Thread or something

@restioson Your code works for me. I run with “start” arg and get “Launching, Serialising”, run it again with “resume” arg and get “Deserialising, Finished”

(kryo version 4.0.0, kotlinx.coroutines version 0.16, kotlin version 1.1.2-5, JVM version 1.8.0_131)

hmm