-
Notifications
You must be signed in to change notification settings - Fork 84
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
Misleading error feedback when several clients fanout at the same time #839
Comments
Had a look on the user-provided logs in #832 and it seems we get the This applies to any state transitions via chain transactions (Collect, Close, Contest) which consume the same UTxO to advance the head life cycle on-chain. |
Our options are not great:
Besides: it would be perfectly fine to ignore this if we see the head advance correctly into the next state. Should we "tone down" the message of this error as it is something which is not so severe? Also: This also reminds us from the "pending transaction" situation where we made the TUI block before submitting another transaction. Next step: Spend 1-2 hours to analyze this situation (either on |
Context & versions
0.10.0 unstable
Steps to reproduce
Actual behavior
The head fanout does success but all but one party will return to the client:
PostTxOnChainFailed
which makes the user confused about what happened.#832 contains more details with error logs from one node.
Expected behavior
If the fanout succeed, no party should see no error.
Extra Information
The fanout transaction needs to spend the output of the close transaction (or the last contest). There is only one such output so if we have several parties trying to spend this output in a fanout transaction, of course, only one of these transaction will succeed and the other transactions will fail.
The hydra-node whose transactions fail would receive an error of the form:
Are we able to figure out that this is an ok error and, either ignore it, or raise a
AlreadyFanedOut
error to the client?The text was updated successfully, but these errors were encountered: