Open josteinaj opened 8 years ago
Don't know why this happens, the webui shouldn't be waiting for the engine before returning a response. Maybe it's just that there's not enough cpu time for the webui to return something that causes this. Moving it to the backlog for now.
If the engine is running at 100% CPU and are unable to respond to requests from the Web UI, then the Web UI seems to be unable to respond to requests from the browser. The browser should instead get a /jobs or
/jobs/{id}
(etc) view with a "waiting for response from engine" message, rather than no response at all.