-
Notifications
You must be signed in to change notification settings - Fork 614
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
Add codespace to NewErrorAcknowledgement #5736
Comments
Discussed this and decided to add a new |
Sounds good to me, thank you. We'd use that in wasmd as soon as it is available. |
@webmaster128 We are going to release this in v8.2.0 (in Q2, most likely first half of the quarter, but will give a more accurate timeline later on). |
Thanks, no rush. I think I can even copy the function if needed in the meantime |
@webmaster128 We have released this addition in v8.3.0. |
Right now,
NewErrorAcknowledgement
only stored an error code without the corresponsing codespace. But the codespace is an incomplete identifier for an error since e.g. sdk/5 is a different error than wasm/5. Having this codespace available would be a huge step forward without creating significant risk of non-determinism. We'd only require that a codespace of an error does not change in a patch release, which is not too much to ask IMO.So what I would like to propose is this diff:
This diff is a compromise between the error code alone and the full error message.
Some related discussions around that matter:
Furthermore I'd like to promote
<codespace>/<code>
as a notation for error codes to highlight that the number is namespaced under the codespace.Please let me know if I got something wrong here.
The text was updated successfully, but these errors were encountered: