Closed ederenn closed 5 years ago
this probably happens when the ForceGetTaskResult
message is sent the second time (after the timeout) after having been sent the first time earlier...
@shadeofblue - what would be the best way to reproduce? Which test?
@dybi I believe this happens in case of a ForceGetTaskResult
message since it has two modes of sending - in one case it's sent directly after a download error and the other if a download doesn't succeed before a timeout happens ...
and I think there are (were?) actually two issues there:
1) the second ForceGetTaskResult
was not cancelled after the first was sent (maybe the cancellation of the delayed message happens only on success and is not done on explicit failure)
2) the sending mechanism doesn't check if a signature exists and tries to sign the message the second time
Encountered on:
'GOLEM Version: 0.16.1+dev163.g4d164a7' 'Protocol Version: 28-testnet' 'golem_messages Version: 2.10.0'
during computations of a task in logs and in console window: