eclipsesource / eclipsesource/papyrus-seqd
Routing of self-messages that start/finish executions
Open
bug
message
prio_highest
- Dominant language
- Java
- Stars
- 1
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
When a self-message starts or finishes an execution specification, then its routing is messed up as shown in the screenshot below. A self-message without any execution is fine. But then if it is later connected to an execution, its breaks in the same way as a new synchronous self-call with execution.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.