-
Notifications
You must be signed in to change notification settings - Fork 88
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
Each client ShouldPostFanout
when observing the OnCloseTx
#279
Comments
ghost
pushed a commit
that referenced
this issue
Mar 22, 2022
This only adapt the behaviour test to express the expected logic change.
ghost
pushed a commit
that referenced
this issue
Mar 22, 2022
ghost
pushed a commit
that referenced
this issue
Mar 22, 2022
ghost
pushed a commit
that referenced
this issue
Mar 22, 2022
Instead, report the error in logs. This reported errors are lame because of the lack of proper JSON support in dependent libraries so we should improve this situation by providing our own or report upstream. We should also report the failure to the end-user possibly by throwing a `PostTxError`.
ghost
pushed a commit
that referenced
this issue
Mar 22, 2022
This code does some arguably ugly things to ensure the failures in the tx submission thread are thrown into the postTx callback's thread in order to be caught at the Node level and not crash. The TQueue for submission should probably be simplified to a TMVar or something as evertyhing is synchronous now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We usually have Heads with very short contestation periods (10sec) and on testnet that is too quick after seeing the
Close
client input.Instead all hydra nodes should try to fanout by scheduling a
ShouldPostFanout
when seeing theOnChainTx
event.The text was updated successfully, but these errors were encountered: