Events that end scopes are not logged

[sombrek]

Describe the Bug

Some intermediate and end events that result in ending a scope (directly or indirectly via event sub processes) are not logged:

Those events are: error, interrupting escalation, cancel, interrupting signal, termination.

Steps to Reproduce

1. Open scope-ending.bpmn.txt in demo
2. Select any outgoing path from the exklusive gateway
3. Start process
4. Notice the none end event is logged, but others, e.g. terminate are not logged at all

The visual demo in #224 shows the log, too.

Expected Behavior

These events should be logged like any other event.

Environment

• Library version: 0.38.0

[nikku]

@sombrek Do you mind attaching a small screen recording with your bug reports? This makes it simpler to "establish context", and hence understand the urgency of your reports.

Edit: I simply inlined the one you linked. What would be your expected behavior there?

[nikku]

Moving to backlog, as I don't see any "bad consequences" of the current behavior.

[sombrek]

What would be your expected behavior there?

I'd expect a log entry "End Event". Or is there any specific reason those events aren't logged?

[nikku]

That makes sense, and your visual demo makes it crystal clear. 🏁

[nikku]

Moving to backlog for the moment.