I assume DA is really busy now but it sounds like there’s a fix for the issue which is promising.
Thanks everyone who contributed to this very helpful thread, particularly Juha for even running some tests. I’ll try to add some logic to make the error less fatal for a short term fix. regards, David K > On Sep 27, 2017, at 2:14 PM, Richard Haselgrove > <[email protected]> wrote: > > It should be pointed out that the fix for this problem > (eaf200e54d4d0bb0ce2ea84ec4f21409d7a80eb6) was available and drawn to David's > attention before v7.8.2 was even built, let alone made the recommended > version. > > > On Wednesday, 27 September 2017, 21:52, Juha Sointusalo > <[email protected]> wrote: > > > On 27 September 2017 at 23:39, David E Kim <[email protected] > <mailto:[email protected]>> wrote: > > > Thanks for running these tests! > > > > So is it a windows only issue? It appears so for R@h. <mailto:R@h.> > > > > Yep. > > Who is responsible for the BOINC client releases? > > > > David Anderson. > > -Juha > _______________________________________________ > boinc_dev mailing list > [email protected] <mailto:[email protected]> > https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev> > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > > _______________________________________________ boinc_dev mailing list [email protected] https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
