You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following this comment, we should figure out how to deal with errors and error codes in the kernel that can come from multiple sources and belong to different categories. For example, the note scripts like P2ID have their own error codes and we include and export them in our auto-generated kernel errors. Should we perhaps export them separately from kernel errors since they are not strictly kernel related?
How should it be done?
We need to think about it.
When is this task done?
When we have come to a conclusion and possibly implemented it.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I think the main problem here is figuring out how to supply error mappings to the transaction host dynamically (rather than assuming that there is only a single static array of errors).
What should be done?
Following this comment, we should figure out how to deal with errors and error codes in the kernel that can come from multiple sources and belong to different categories. For example, the note scripts like P2ID have their own error codes and we include and export them in our auto-generated kernel errors. Should we perhaps export them separately from kernel errors since they are not strictly kernel related?
How should it be done?
We need to think about it.
When is this task done?
When we have come to a conclusion and possibly implemented it.
Additional context
No response
The text was updated successfully, but these errors were encountered: