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

graph should not eat the storaged‘s error code? #4958

Closed
Nicole00 opened this issue Nov 30, 2022 · 2 comments
Closed

graph should not eat the storaged‘s error code? #4958

Nicole00 opened this issue Nov 30, 2022 · 2 comments
Labels
type/enhancement Type: make the code neat or more efficient wontfix Solution: this will not be worked on recently
Milestone

Comments

@Nicole00
Copy link
Contributor

General Question

When storaged happens leader change error, storaged return E_LEADER_CHANGED. When graphd get storaged's E_LEADER_CHANGED, it return E_EXECUTION_ERROR with message Storage Error: The leader has changed. Try again later..
should graphd return E_LEADER_CHANGED error code too?

@github-actions github-actions bot added affects/none PR/issue: this bug affects none version. type/none severity/none Severity of bug labels Nov 30, 2022
@HarrisChu
Copy link
Contributor

prefer a new error code in graphd, graphd should never return error code from storaged.

@Sophie-Xie Sophie-Xie added the type/bug Type: something is unexpected label Nov 30, 2022
@Sophie-Xie Sophie-Xie added this to the v3.4.0 milestone Nov 30, 2022
@Sophie-Xie Sophie-Xie added the need to discuss Solution: issue or PR without a clear conclusion on whether to handle it label Nov 30, 2022
@HarrisChu HarrisChu added type/enhancement Type: make the code neat or more efficient and removed type/bug Type: something is unexpected severity/none Severity of bug affects/none PR/issue: this bug affects none version. labels Dec 1, 2022
@Sophie-Xie Sophie-Xie assigned MuYiYong and unassigned dutor Dec 2, 2022
@Sophie-Xie Sophie-Xie removed the need to discuss Solution: issue or PR without a clear conclusion on whether to handle it label Dec 5, 2022
@xtcyclist xtcyclist added the wontfix Solution: this will not be worked on recently label Dec 21, 2022
@xtcyclist
Copy link
Contributor

To the graphd and to the user, errors from the storaged like this happen in the execution phase. It is indeed an execution error. Nothing wrong here. And, we shall not simply pass storaged's internal errors to the users, considering that graphd is the upper-most layer.

In 5.0, we will have a new system of reporting errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Type: make the code neat or more efficient wontfix Solution: this will not be worked on recently
Projects
None yet
Development

No branches or pull requests

6 participants