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

icees-kg KP is missing a urlRemote and therefore returns 500 from ARS #378

Closed
maximusunc opened this issue Mar 24, 2023 · 7 comments
Closed
Assignees

Comments

@maximusunc
Copy link

It's been noticed that icees-kg is always returning a 500 error from queries to the ARS. I did some investigation and noticed that in all ARS environments, /ars/api/actors shows that icees-kg urlRemote is null, whereas other KPs/ARAs have this field set. I'm not entirely sure how the ARS KP registration works, so please correct me if I'm wrong. Do we need to set a urlRemote in order for the ARS to successfully query icees-kg?

@karafecho

@maximusunc
Copy link
Author

One other thing I noticed was that there were the other non-TRAPI icees instances still listed. kp-icees-kg is the only one that the ARS needs to know about, kp-icees, kp-icees-pcd, and kp-icees-dili should all be removed.

@ShervinAbd92
Copy link
Collaborator

ShervinAbd92 commented Mar 27, 2023

hi @maximusunc, the issue was coming from an extra space between infores and icees-kg in the app folder. once i removed the extra space, urlRemote was returning the url . As for the other icees, even though they are listed, they have been deactivated (active=False) but we can completely wipe them out if you guys prefer that?

@maximusunc
Copy link
Author

Hey @ShervinAbd92 I think we would prefer them removed, just so it's clear that they shouldn't be used in Translator. Thanks!

@ShervinAbd92
Copy link
Collaborator

sure @maximusunc. we can take care of that :)

@ShervinAbd92
Copy link
Collaborator

hey @maximusunc, Mark William just reminded me that the reason we just deactivated them instead of removing them is that all previous query responses from these icees are going to be deleted from our records. i am not sure, if this is what we want?

@maximusunc
Copy link
Author

@karafecho what do you think?

@karafecho
Copy link

@ShervinAbd92 : Max and I discussed this, and we agree that you should go ahead and remove all prior icees instances EXCEPT icees-kg. Thanks!

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

5 participants