-
Notifications
You must be signed in to change notification settings - Fork 22
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
Improve Agent query endpoint not TRAPI compliant #52
Comments
@brettasmi Here is an example of the test query and some details of the POST response we are currently getting.
|
Thanks for the report Noel. I will try to recreate the issue locally and fix it. A quick glance suggests that query should be returning a 200 without results. |
based on the ARS call today, (im)Prove is compliant, but there is an error like "method is not allowed" when a TRAPI query is sent from the ARS. When it is sent directly, (im)Prove works fine. |
From the logs, I can see that there seems to be an unexpected It would be helpful to see the query that you are attempting to make so that I can try to reproduce it. Also, see https://github.com/suihuanglab/improving-agent/blob/main/examples/improving_agent_examples.ipynb for working TRAPI 1.0 examples |
After some debugging with Mark yesterday, we discovered a couple things:
|
registration is completed |
One of the test queries we currently use to probe service status is a one-hop query, and this is currently returning a non-status 200 response for improve agent. We have yet to fully converge on a standard for error responses from Reasoner API services, but the current convention is to return a status 200 response if the message was received and is TRAPI compliant. See, for example, NCATSTranslator/ReasonerAPI#140
The text was updated successfully, but these errors were encountered: