Async Stack should distinguish between sending the same object twice
Currently the past of message is traced with message only. It causes a side effect of a 'history merge' in following snippet:
Briefly, when I move toward future I send message to actor1 only (I trace this time line only). But then when I try to go back into the past I see that in my time line both sendings took place.
It seems that the sender and triggering message should be included into message flow history. It won't cover the following case:
we won't be able from where actually the message has been sent but for message flow it does not matter.
Remark:
test following snippet:
As a result these two time lines should be separate.
case msg =>
actor1 ! traced_message
actor2 ! traced_message
Briefly, when I move toward future I send message to actor1 only (I trace this time line only). But then when I try to go back into the past I see that in my time line both sendings took place.
It seems that the sender and triggering message should be included into message flow history. It won't cover the following case:
case msg =>
actor1 ! traced_message
...
actor1 ! traced_message
we won't be able from where actually the message has been sent but for message flow it does not matter.
Remark:
test following snippet:
case msg1 =>
actor1 ! traced_message
case msg2 =>
actor1 ! traced_message
As a result these two time lines should be separate.
Leave a comment
on 2015-12-08 09:05 *
By Iulian Dragos
Summary changed from Asyn Stack Trace improvement to Async Stack should distinguish between sending the same object twice
Move ticket to next milestone.