[Feature request] Detect WORK_QUIT (404) response from FAH server when uploading finished WU

[Kelvin]

Hi harlam357,

Recently I encountered a case where the WU completed successfully (FINISHED_UNIT) but FAH server didn't award point (server responsed WORK_QUIT).

After reading some old posts in FAH forum, I suspect that the reason is because my PC (more specifically, my GPU) was not properly overclocked and the WU result submitted to FAH server failed some tests and was rejected.

However, HFM.NET was not able to detect that error (although it also didn't record that WU as FINISHED_UNIT in the Work Unit History page)

Please add the new feature to detect that WORK_QUIT (404) response from FAH server and add that record into the Work Unit History as a bad WU

This will help users to quickly detect if the PC is unstable (due to overclocking/overheating/etc.)

Example log for WORK_QUIT (404):

06:30:09:WU01:FS01:0x21:Completed 5000000 out of 5000000 steps (100%)
06:30:10:WU01:FS01:0x21:Saving result file logfile_01.txt
06:30:10:WU01:FS01:0x21:Saving result file checkpointState.xml
06:30:11:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
06:30:11:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11726 run:0 clone:1958 gen:406 core:0x21 unit:0x000002178ca304e75b95bafb59c2a429
06:30:11:WU01:FS01:Uploading 12.43MiB to 140.163.4.231
06:30:15:WU01:FS01:Upload complete
06:30:15:WU01:FS01:Server responded WORK_QUIT (404)
06:30:15:WARNING:WU01:FS01:Server did not like results, dumping
06:30:15:WU01:FS01:Cleaning up

In normal case, the server will return WORK_ACK (400) with final estimation of points

02:08:08:WU00:FS00:Server responded WORK_ACK (400)
02:08:08:WU00:FS00:Final credit estimate, 2280.00 points

Regards,

Kelvin