Improve ways to identify future callbacks

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It's currently very difficult to determine the source code origin of a future callback being executed.

      This would make it easier to identify the problematic code when invariants inside the future code like this is triggered if there are more info available.

      It would also potentially allow easier ways to examine the tasks that are pending in the task executor.

            Assignee:
            Unassigned
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: