Miner restarts on work submission failure

[aolieman]

I still get regular ETIMEDOUT errors from Axios calling the RPC. When the network error happens while submitting work, instead of retrying the submission, the homestead server restarts the whole mining job.

Is this the intended behavior?

Here's an example from my logs:

[CPU] Hash Rate: 2.79 MH/s
{
  "hash": "0000000ad6dbafac2c13a41ed5bc666c6fd4b1b9ef1d7caa5701d7993205fee5",
  "nonce": 187959518
}
====END MINING JOB=====
Farmer GBPZWD5ENV7SWWHAOFZ6YYCAY2VGKZLNDUJDWQJLA3OQPJ7W56KM7ADG process completed: code(0)
Farmer GBPZWD5ENV7SWWHAOFZ6YYCAY2VGKZLNDUJDWQJLA3OQPJ7W56KM7ADG worked [0000000ad6dbafac2c13a41ed5bc666c6fd4b1b9ef1d7caa5701d7993205fee5, 187959518] for 1434
Farmer GBPZWD5ENV7SWWHAOFZ6YYCAY2VGKZLNDUJDWQJLA3OQPJ7W56KM7ADG submitting work later (minimum time: 141 sec)
Current block is 1434, elapsed 2 min 23 sec
Farmer GBPZWD5ENV7SWWHAOFZ6YYCAY2VGKZLNDUJDWQJLA3OQPJ7W56KM7ADG could not submit work for block 1434: {"cause":{"code":"ETIMEDOUT"}}
Current block is 1434, elapsed 3 min 3 sec
Farmer GBPZWD5ENV7SWWHAOFZ6YYCAY2VGKZLNDUJDWQJLA3OQPJ7W56KM7ADG process started with command: 1434,AAAAAApIbPCvaefyJgdk0y1vx9ziWRjFuNzBzyBUODM=,104297,7,GBPZWD5ENV7SWWHAOFZ6YYCAY2VGKZLNDUJDWQJLA3OQPJ7W56KM7ADG,--max-threads,4,--batch-size,10000000,--device,0,--verbose
====MINING JOB=====

[CPU] Mining batch: 104297 block: 1434 difficulty: 7 hash: AAAAAApIbPCvaefyJgdk0y1vx9ziWRjFuNzBzyBUODM=