Errors in code of receptors must be visible in console #1490
Description
I was working on a test fixture CountingContext using Kotlin DSL and couldn't get results I expected from the very simple logic.
It turned out that I used DSL in a wrong way. It caused UnsupportedOperationException on a map object delegate deep inside Protobuf. It wasn't visible at all because we catch exceptions, create errors, and associate them with the dispatched signal. But nothing happens in the console about it. It just goes silently and smoothly, but in a wrong way.
We need to shout about such errors. Otherwise, it takes much time to catch it, and the silence is a disservice.