We've seen in a number of situations in the past that a long running computation may complicate any efforts of debugging backend issues.
Every ExecuteJob must start a separate that monitors its execution and detects/informs of long running computations/deadlocks. Logging such information would be sufficient for starters.
The proposed monitoring could be a) extended to all jobs b) extended to send progress in executing normal jobs to IDE clients
We've seen in a number of situations in the past that a long running computation may complicate any efforts of debugging backend issues. Every
ExecuteJob
must start a separate that monitors its execution and detects/informs of long running computations/deadlocks. Logging such information would be sufficient for starters.The proposed monitoring could be a) extended to all jobs b) extended to send progress in executing normal jobs to IDE clients