-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core: panic checking cancel order checksum #2964
Comments
The only way this can happen is if the |
I can look into this if noone else is. |
We chatted on matrix and maybe the issue is more than just a panic. Its likely this panic occurred because preimage missed came as we were sending the preimage, so simply locking the trade mutex should fix that but there may be a bigger issue causing preimages to be missed. I have an example here using loadbot, where the server sent the preimage 20 seconds before we acknowledged it, and we missed it. This seems excessive on simnet, so it may be that we are waiting in core for some reason (til the end of the epoch?), or locked up, and missing sending preimages. server:
client
|
More logs for the same server and client, these preimages were sent and received in the middle of the others, so its more than strange that we waited somewhere for the previous preimages: server
client:
|
One more, client showed that some of the preimage requests from the batch that failed were received with only a slight delay client
|
Just noticing that it's STACKER:0 That seems to be stuck, thats why there are still notifications inbetween for STACKER:1 |
Sorry to be so chatty here, it seems this is the most important log from client:
|
The text was updated successfully, but these errors were encountered: