-
Notifications
You must be signed in to change notification settings - Fork 4
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
Locations endpoint throwing 500 errors #24
Comments
@crew102 FWIW the presence of cpc_sequence is the cause of the 400 error. I hope this helps narrow down these problems in the api.
|
I wrote a scritp to incrementally add location fields to the query. I found that with matched_subentities_only=true the assignee, cpc, nbr, raw fields and uspc fields shown below caused 500 errors. Below the list is the largest subset of fields that worked, adding any more caused a 500 error. @crew102 Perhaps these fields could be unmapped from the R package until the api is fixed for this endoint?
|
Hi @mustberuss, I suspect that setting If both of these are true:
..Then Let's move any further discussion into a new issue at ropensci/patentsview |
@crew102 just to clarify, I believe you mean the locations endpoint |
In looking at this further, I don't believe there are any troublesome fields. It's the number of groups present that seems to be the problem. With the exception of cpc_sequence's 400, I can query for each group's fields in individual calls to the location endpoint. I now think the complexity of the sql in entitySpecs.php for $LOCATION_ENTITY_SPECS is the problem when multiple groups are present. I get back this X-Status-Reason header with the 500.
I'm wondering if the call times out and throws the 500 when too many groups are present. As @crew102 mentioned originally, for other endpoints he can request every possible field successfully in a single api call. It's just the locations endpoint that has this problem. Successful individual request:
with credit to @crew102 for suggesting we look at the (now vindicated) troublesome groups. |
Thanks for debugging this so thoroughly, we've added this to our issues tracker and will follow up when the problem is resolved! |
Now I'm seeing a 500 error thrown on three of the endpoints (cpc_subsections, nber_subcategories, uspc_mainclasses) when matched_subentities_only is false and all possible fields are requested.
If I set mtchd_subent_only=TRUE then only the locations endpoint throws a 500 as we saw before. |
Thanks for pointing this out -- this is definitely an issue and we are looking into it! We'll get back to you once we've fixed the issue! |
Hi -
For each endpoint except for locations, I'm able to request all of the possible fields and I get the data I would expect. When I request all of the retrievable fields for the locations endpoint, I get either a 400 or 500 error. For example, see the example request below, which resulted in a 400 error. Do you know why this would be the case? (note, we know why the 400 errors are happening, and this is not a separate issue: #29 )
Thanks,
Chris
The text was updated successfully, but these errors were encountered: