Skip to content
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

Node Normalizer Url #27

Open
cmaceves opened this issue Oct 9, 2023 · 3 comments
Open

Node Normalizer Url #27

cmaceves opened this issue Oct 9, 2023 · 3 comments

Comments

@cmaceves
Copy link

cmaceves commented Oct 9, 2023

Hello! I've been using this tool, and last week I began to get a 500 error when running benchmark_evaluate. I traced it back through the code and realized that this url is the culprit for the internal server error. Is there a better URL I can use to avoid this error?

@gaurav
Copy link

gaurav commented Oct 9, 2023

That URL should work! What command did you run that caused the error? Do you know which CURIEs you are trying to normalize at the time?

@cmaceves
Copy link
Author

I was running a python script containing the lines
from benchmarks.eval import evaluate_results
results = evaluate_results("DrugCentral_creative", direct) however I'm actually unable to replicate my initial error now.

@ngk5
Copy link
Contributor

ngk5 commented Oct 12, 2023

We first noticed the 500 Internal Server Error on 9/26, and I believe there was an upgrade to Node Norm being done that day. Since the existing URL may be more unpredictable than other instances, could/should the URL be changed to prod or a different instance that's more stable (eg. https://nodenorm.transltr.io/1.3/get_normalized_nodes) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants