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

Use vterrors to store stack traces #4556

Merged
merged 2 commits into from
Mar 3, 2019
Merged

Use vterrors to store stack traces #4556

merged 2 commits into from
Mar 3, 2019

Conversation

systay
Copy link
Collaborator

@systay systay commented Jan 28, 2019

No description provided.

@systay systay requested a review from sougou as a code owner January 28, 2019 13:30
@systay systay force-pushed the errors branch 4 times, most recently from cb6d6d6 to 5d1773f Compare January 29, 2019 09:31
@systay systay force-pushed the errors branch 5 times, most recently from a86a398 to 63ddfeb Compare February 25, 2019 17:03
* Use vterrors in few places
* Make stack trace display the default
* More unit testing around error handling

Signed-off-by: Andres Taylor <antaylor@squareup.com>
Signed-off-by: Andres Taylor <antaylor@squareup.com>
Copy link
Member

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
I'm not sure I agree with using RPC error codes everywhere, but vterrors seems to require that, so that's fine.
Upon discussion with @sougou, learned that the error codes are designed to be generic, not just for RPCs.

@deepthi deepthi merged commit 6585831 into vitessio:master Mar 3, 2019
systay pushed a commit that referenced this pull request Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants