If this discussion has come up before, I apologize.
Should bad downloads be recorded in History? The following d/l event showed up in Tasks (in the proper color) as "Download error" but doesn't appear in History:
Quote4+1 [hostname]
7465 yoyo@home 7/24/2010 00:04:04 Started download of ogr_100703001006_78-in.og2
7466 yoyo@home 7/24/2010 00:04:06 Incomplete read of 43.000000 < 5KB for ogr_100703001006_78-in.og2 - truncating
7467 yoyo@home 7/24/2010 00:04:06 Finished download of ogr_100703001006_78-in.og2
Note that
<report_results_immediately> was set true at the time, so it wasn't displayed in Tasks for very long--possibly within your 15 sec cycle. But saving that exception, would you expect such a busted download to be in the History?
Quote from: jjwhalen on July 24, 2010, 07:34:37 AM
If this discussion has come up before, I apologize.
Should bad downloads be recorded in History? The following d/l event showed up in Tasks (in the proper color) as "Download error" but doesn't appear in History:
Quote4+1 [hostname]
7465 yoyo@home 7/24/2010 00:04:04 Started download of ogr_100703001006_78-in.og2
7466 yoyo@home 7/24/2010 00:04:06 Incomplete read of 43.000000 < 5KB for ogr_100703001006_78-in.og2 - truncating
7467 yoyo@home 7/24/2010 00:04:06 Finished download of ogr_100703001006_78-in.og2
Note that <report_results_immediately> was set true at the time, so it wasn't displayed in Tasks for very long--possibly within your 15 sec cycle. But saving that exception, would you expect such a busted download to be in the History?
There is no valid tasks to begin with and BT only records tasks.
A download error, is an error before it technically becomes a task.
Quote from: fred on July 24, 2010, 09:32:53 AM
A download error, is an error before it technically becomes a task.
Got it...except that displaying it in the "Tasks" list rather says it technically
is a task :)