-
Notifications
You must be signed in to change notification settings - Fork 3
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
More informative errors for neuprint_fetch_custom? #38
Comments
@romainFr If you give me a query with error, can show you how to get that. |
@romainFr can you give an example here? |
If I run a large query, in neuprint explorer I'd get a message expliciting that the problem is a time out (this happens with path queries easily):
Whereas in neuprintr, we only return (other example, when querying a shortest path with identical neurons in the input and output side, we get a bad request, whereas neuprint explorer returns:
|
Thanks @romainFr. But can you give an actual R snippet that fails? |
I think the issue is that the server returns an error code which triggers an R error before we ever get to inspect the details of the request to extract more information. Lines 15 to 26 in ea20c16
Basically if we get a 400 status instead of throwing an error immediately we should extract the error details and then throw the error. |
|
In neuprint explorer, you get error messages that detail why a given query fails. If there's a way to grab those through the API that would be more useful that the HTTP error codes we're now getting.
The text was updated successfully, but these errors were encountered: