-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Remove vtrpc.LegacyErrorCode #8456
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look correct to me. You're gonna need to make proto
again because I merged an updated version of the compiler this morning.
Besides that, I don't know whether the LegacyErrorCode
is legacy enough to be removed already!
3c39e53
to
4964352
Compare
Hmm, it looks like this is failing on the java stuff, do you have any idea how I update that to stop expecting these types?
more specifically, is this client codegen'd from the protos somehow? i don't see a make target anywhere. i can obviously just delete the references to the old types, but i am not sure if there's something else i should be doing since i'm not familiar with the java client |
@systay maybe you know how this Java stuff is generated? |
hmm... if it's not created with |
The only thing to change is removing the switch condition in |
It has been "legacy" for 4 years now, so it should be safe to just drop. Signed-off-by: Andrew Mason <[email protected]>
Signed-off-by: Andrew Mason <[email protected]>
Signed-off-by: Andrew Mason <[email protected]>
403a352
to
e2a37bc
Compare
It has been "legacy" for 4 years now, so it should be safe to just drop.
Signed-off-by: Andrew Mason [email protected]
Description
Related Issue(s)
Checklist
I wasn't sure what component to pick since it pretty much affects all of them (since they all use vtrpc.RPCError in some form or fashion)
Deployment Notes