-
-
Notifications
You must be signed in to change notification settings - Fork 393
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
fix: retry compilation if grpc client needs to be reinitialized #2548
base: main
Are you sure you want to change the base?
Conversation
This change resolves the issue where the intersection of `ServiceError` error codes of type `number` resulted in the `never` type due to conflict between number and `State` enum if `StatusObject`
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.
It's looking great.
Why not handle the error on the backend without sending it back to the FE? Is there a technical limitation? Thank you! (Related #2500)
|
||
if ( | ||
ServiceError.isInvalidArgument(error) && | ||
error.details.includes('instance is no longer valid') |
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.
What should happen when the selected language is, for example, German, and there is a translation for this error message for the CLI?
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.
I'm now extracting the error type from the error metadata 👍
375571e
to
00a773c
Compare
Thanks for the review @dankeboy36! |
00a773c
to
7bc2a1e
Compare
Motivation
Closes: #2547
Change description
Catch invalid instance error during compilation, refresh grpc client and retry.
Other information
Reviewer checklist