-
Notifications
You must be signed in to change notification settings - Fork 43
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
getbalance assertion after closechannel eth #2028
Comments
Since it is simnet I assume this is vector? If so, needs to be handled @erkarl Ideas? |
Yeap it is vector. Most likely this case can be reproduced when updating old version of xud (without vector) to a new one. |
Think it's caused by the mismatch in token addresses. I assume it doesn't reproduce with a fresh env? |
yeap, did not get it on fully new env. |
That error generally means that we're trying to assign an illegal value to a grpc field, like a negative number to an unsigned int, or a value greater than 2^64 for a 64 bit int. |
So.. do we want to prevent such values to be assigned to a grpc field, if not I guess we can close here? |
Background
Today I tried to withdraw funds from eth channel to connext wallet and after withdrawing my getbalance call started to return assertion error. I checked xud and connext logs, xud was contain only assertion and i found nothing interesting in connext logs.
After that I removed and initialized new env again to reproduce the assertion appearing again to get reliable steps, but i was not able to get it again, so it is something floating. :(
Xud logs:
Utils output:
The text was updated successfully, but these errors were encountered: