Introspection or trace for warning "Action timed out"

[adverley]

The current implementation warns users if actions timed out which is really useful. It might be handy to know the source of the timed-out action.

[tlpss]

Agreed. Errors (instead of warnings) would do this but I thought it would not always be desirable to raise an error.
If we believe errrors are fine, we get the trace for free. If not we can use inspect to print the stack. https://stackoverflow.com/questions/1156023/print-current-call-stack-from-a-method-in-code

@adverley what do you think? should we raise errors or warnings?

[adverley]

It doesn't feel right to crash other people their application because they had a timed-out action. I'm in favor of keeping the warning and printing part of the stack with inspect.