3.0b1 - Timeout function killing process during prepare step about super HOT 3 CLOSED

First, the "download" workflow is actually two steps, download followed by a prepare. In my testing, the prepare log entries were slower to respond than the download log entries, but never more than five minutes between updates.

However, it looks like in your testing repair. Log entries are returning slower than five minutes apart. Feel free to modify the '$defaultTimeoutSECONDS' variable for a longer time out.

If that was successful for you, please provide feedback as to what your longest log entry delay time was.

from super.

Ah ok, I understand now. The timeout isn't based on the total time for the prepare to complete; it's based on the time between the log entries posted in the update.log during the prepare.
You're right; 5 minutes seems like a long time between entries. I set it for 7 minutes to test, and It looks like the longest gap between entries was 5 minutes and 30 seconds. One other gap was 1 minute, and the rest were about 5 to 15 seconds.

from super.

It looks like several more testers are running into this same issue. I think if it’s increased to 360 seconds that should cover the longest gap I’ve been seeing.

from super.