-
Notifications
You must be signed in to change notification settings - Fork 251
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
jrpc - make cleaner error message #633
Comments
Can you say what you actually called? because in theory a 404 is intercepted and you get a FetchError in https://github.com/fortio/fortio/blob/master/jrpc/jrpcClient.go#L165 but maybe it should be closer to https://github.com/fortio/fortio/blob/master/jrpc/jrpcClient.go#L169 a sample repro would help understand your use case |
talked offline, and improving the error message in upcoming pr |
ldemailly
added a commit
that referenced
this issue
Oct 24, 2022
…r shortcut jrpc.GetArray(). Also fix #633
ldemailly
added a commit
that referenced
this issue
Oct 24, 2022
…hortcut: `jrpc.GetArray()` (#634) * add test for slice/array returned from jrpc calls as well as a cleaner shortcut jrpc.GetArray(). Also fix #633 * update test accordingly to error message change * test the nil slice case * prep for 1.38.2, would in theory be 1.39.0 as there is a new api but this is a super minor addition
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had the following error:
This was due to a bug on my end (wrong path to request). Yet I found the error confusing and it took me a while to get it. What would make it more clear/easier is a format like:
The text was updated successfully, but these errors were encountered: