@sjka already started looking into it. But I think it is correct that the handler is disposed on a thing type change - a different handler might be instantiated afterwards, right?
But the shutdown process of a handler might be optimized as currently the callback is removed before the handler is disposed, so it does not have a clue that this might have happened.
Yes - I donât disagree - just wondering if thereâs a better way that allows the handler to complete what itâs doingâŠ
Hopefully the change I made will at least fix the current issue.
Thanks.
I have one node that I can not initialize (due to this error). The others got the error, but finally initialized.