shadeofblue

@cryptobench which yagna version are you using?

@golemfactory/core I believe it has to do with the timeout on the websocket itself - could you confirm or deny that?

@johny-b is that something that's included in your refactoring plan? if yes, please plan it accordingly, if not, please just close it for now

hmm.... it would be good to see the task data for the ACCEPTED/REJECTED messages

so, most likely a matter of catching the relevant 404 and just maybe issuing a warning to the log... plus, it might warrant an integration test...

> PR that fixes allocation timeout: #926 it does not _fix_ the issue, it's a work-around...

*market* ... plus, I guess the rescoring should be somehow bound to the job - since we might be scoring offers differently depending on the demand ... so, it seems...

@mbenke we're adding this issue to our backlog and will try to handle it in the next iteration

@mbenke it would be good to know the impact and severity though

rather than removing it, I'd have it called when it _should_