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.

Sign up for GitHub

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

Jump to bottom

Difficult to categorize remote errors #2

Open
KB1RD opened this issue Jul 7, 2020 · 0 comments
Open

Difficult to categorize remote errors #2

KB1RD opened this issue Jul 7, 2020 · 0 comments
Assignees
@KB1RD
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@KB1RD
Copy link
Owner

KB1RD commented Jul 7, 2020

Remote errors are serialized as objects. When the result of call is passed back, it is assumed that the second value in the argument array (since this is just a type of send) is an error. The values in it are Object.assigned to a ForwardedError. Because of this, every error thrown by a call is an instance of ForwardedError. This makes errors difficult to categorize when they are received.
@KB1RD KB1RD added enhancement New feature or request help wanted Extra attention is needed labels Jul 7, 2020
@KB1RD KB1RD self-assigned this Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KB1RD KB1RD

Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KB1RD