-
Notifications
You must be signed in to change notification settings - Fork 0
assert grpc call errors #6
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
Conversation
Signed-off-by: Eguzki Astiz Lezaun <eastizle@redhat.com>
faa1487 to
f022ba0
Compare
| request, | ||
| timeout_milliseconds, | ||
| ) | ||
| .unwrap_or(Ok(0)); |
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.
You seem to change this for a Err now, to get the previous behavior... that was already confusing, but that's now a new pattern, I don't think this makes sense...
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.
So why the Result here? if the Err path gets dropped on the floor?
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 get rewrapped in an Option::Some always... Now I get it
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.
... other than when it isn't expected...
|
I was thinking we should bring these changes to proxy-wasm#17 wdyt @alexsnaps ? |
Expect from the GRPC call to return error as well.