You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's hard to trace the flow of async, event-oriented code. One thing that I've found that helps is passing along the stacktrace of the caller. The listener can then access and print that (e.g. from a property on the Action) to see exactly how the Action came to be called.
Thoughts?
The text was updated successfully, but these errors were encountered:
It looks like you have not included any tickets in the title of this issue. Please create a ticket for this issue, or click here to have Rosie create one for you.
rmconsole2-wf
changed the title
Store StackTrace when Action is called for easier debugging and tracing
CP-3163 Store StackTrace when Action is called for easier debugging and tracing
Dec 13, 2016
It's hard to trace the flow of async, event-oriented code. One thing that I've found that helps is passing along the stacktrace of the caller. The listener can then access and print that (e.g. from a property on the Action) to see exactly how the Action came to be called.
Thoughts?
The text was updated successfully, but these errors were encountered: