You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calls to the node normalizer endpoint through TranslatorImplementation lead to an AttributeError as the response is valid JSON but appears to just be "detail: "Not Found"", even for cases where an input CURIE really should be found.
(and even if it wasn't found, I'd expect the error to be caught).
Example:
$ python
Python 3.9.18 (main, Aug 25 2023, 13:20:04)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from oaklib.implementations.translator.translator_implementation import TranslatorImplementation
>>> ti = TranslatorImplementation()
>>> maps = ti.sssom_mappings("HGNC:11148")
>>> for map in maps:
... print(maps)
...
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/harry/ontogpt/.venv/lib/python3.9/site-packages/oaklib/implementations/translator/translator_implementation.py", line 62, in sssom_mappings
equiv_identifiers = data.get("equivalent_identifiers", [])
AttributeError: 'str' object has no attribute 'get'
The text was updated successfully, but these errors were encountered:
Discovered here in ontogpt: monarch-initiative/ontogpt#224
Calls to the node normalizer endpoint through TranslatorImplementation lead to an
AttributeError
as the response is valid JSON but appears to just be "detail: "Not Found"", even for cases where an input CURIE really should be found.(and even if it wasn't found, I'd expect the error to be caught).
Example:
The text was updated successfully, but these errors were encountered: