DistRTgen: Next batch of work flowing for GPUs

First, GPU work is now flowing for NV CUDA and ATI/AMD OpenCL alike.While, I can make excuses for delays, lack of communication, and so on: everything related to this falls short of the project's goals. First, when work is running low and we do not have the next set queued, we should communicate this. Second, we need to be more flexible for unexpected issues, whether for instance it is lack of developer/admin time or a new set explodes due to errors, we need to not just be ready for our next set but the set after that.Communication is something we need to have at the forefront. On the admin side we have graphs, monitoring, and predictive stats for when work will run out *but* this seems to fail and the reason is simple: we are overly optimistic about the times to test and push a code fix *or* are struggling to use existing deployed code to create useful sets that are not so large and slow as to be unusable.In this particular case there is a bug for the AMD/ATI OpenCL code for ntlm which resulted in the matching mysqlsha1 set that just wrapped up. I believed I could get this code fixed, tested, and deployed in a timely fashion, but should have just released the md5 set that is now in progress. I *thought* we had already done the md5 set as well as being optimistic on fixing the OpenCL bug on ntlm. This batch *should* have and *could* have been released to prevent any interruption in the work flow.I made a placeholder thread, which I will expound on this, including making excuses in the primary forums https://www.freerainbowtables.com/ph...php?f=4&t=4658

More...