JDC panics after receiving RequestTransactionDataError message

[GitGab19]

JDC panics after receiving a RequestTransactionDataError message.
The line of interest is roles/jd-client/src/template_receiver/message_handler.rs:46:9.

For a better context, here's a screenshot of the error, we got it right after the last testnet block mined:

[Fi3]

JDC do not handle request tx data error we should decide what to do when it happen. This is not straightforward cause a TP that is not able to provide txs data for tx that have been included in the block by the TP should likley be considered unreliable and the connection should be closed. But maybe we prefer to try again? Some discussion is needed here.

[Fi3]

Removed tha bug label as it is a new feature more than a bug

[GitGab19]

In the specific case mentioned here, JDC received the RequestTransactionDataError for template 1946. That was the first template created after the new block was found. Right after that, a new future template was created and sent to JDC.
Could it be that TP is not able to get information about previous templates?

[Sjors]

Templates are forgotten after a new block is found so that's probably what happened. It's on my list to address that.

[GitGab19]

Templates are forgotten after a new block is found so that's probably what happened. It's on my list to address that.

Hi @Sjors, I can confirm you that every time we get this error is right after a new block is found and a SetNewPrevHash is received.