Skip to content
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

Figure out how to deal with errors from multiple sources and categories #910

Open
PhilippGackstatter opened this issue Oct 8, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@PhilippGackstatter
Copy link
Contributor

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

@bobbinth
Copy link
Contributor

bobbinth commented Oct 9, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants