Actions
Feature #8925
openProcess error traces with timeout
Start date:
06/06/2018
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
Sometimes Bridge can process error traces infinitely due to some issues. This can result in very strange and unexpected consequences. So, I suggest to specify some reasonable timeout for processing error traces, say, 30 seconds, and to print an error after it rather than to hang.
BTW, I don't think that this has much sense for other places, although similar issues can be anywhere, because of some operations can take really much time, e.g. downloading/uploading verification job trees can take several hours.
Actions