If repeats was > 1 (for a GPU miner), the client would only send one no_solution message for the whole batch of nonces, and no no_solution message if even one cycle was found.
This change sends an individual no_solution message for each relevant nonce. Sending one combined message would be more economical, but would require a protocol upgrade.
For better performance, an async_call() method is used. This ignores the reply from the server, and is only used for the no_solution message, which doesn't really return useful data anyway.
Tested (and running) on my 1080ti miner.
If `repeats` was `> 1` (for a GPU miner), the client would only send one `no_solution` message for the whole batch of nonces, and no `no_solution` message if even one cycle was found.
This change sends an individual `no_solution` message for each relevant nonce. Sending one combined message would be more economical, but would require a protocol upgrade.
For better performance, an `async_call()` method is used. This ignores the reply from the server, and is only used for the `no_solution` message, which doesn't really return useful data anyway.
Tested (and running) on my 1080ti miner.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
If
repeatswas> 1(for a GPU miner), the client would only send oneno_solutionmessage for the whole batch of nonces, and nono_solutionmessage if even one cycle was found.This change sends an individual
no_solutionmessage for each relevant nonce. Sending one combined message would be more economical, but would require a protocol upgrade.For better performance, an
async_call()method is used. This ignores the reply from the server, and is only used for theno_solutionmessage, which doesn't really return useful data anyway.Tested (and running) on my 1080ti miner.