We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The signer can get stuck when an open message has expired on the aggregator (as described in https://discord.com/channels/826816523368005654/1014019542504185876/1328667162524516384 and https://discord.com/channels/826816523368005654/1014019542504185876/1328523813352116327):
Have the signer consider a message signed even if the aggregator returns an error because of an expired open message when the signature is submitted.
GONE
CertifierServiceError
Expired
register_signatures
CONFLICT
The text was updated successfully, but these errors were encountered:
2506
/register-signatures
dlachaume
Successfully merging a pull request may close this issue.
Why
The signer can get stuck when an open message has expired on the aggregator (as described in https://discord.com/channels/826816523368005654/1014019542504185876/1328667162524516384 and https://discord.com/channels/826816523368005654/1014019542504185876/1328523813352116327):
What
Have the signer consider a message signed even if the aggregator returns an error because of an expired open message when the signature is submitted.
How
GONE
HTTP code when theCertifierServiceError
returned isExpired
GONE
HTTP code inregister_signatures
function to use the error message returned by the aggregatorCONFLICT
handling of theregister_signatures
signature functionThe text was updated successfully, but these errors were encountered: