bjjdjango
bjjdjango4mo ago

Is anyone else getting this error? (This

Is anyone else getting this error? (This is when I am trying to use the dataset to evaluate and score pretty much as what the dataset notebook example has). I added a comment to an existing bug, but I'm not sure if that's the same issue, so I will also share here:
.../eval.py
Traceback (most recent call last):
File ".../eval.py", line 191, in <module>
main()
File ".../eval.py", line 100, in main
handler = item.get_langchain_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File ".venv/lib/python3.11/site-packages/langfuse/client.py", line 2553, in get_langchain_handler
self.link(
File ".venv/lib/python3.11/site-packages/langfuse/client.py", line 2518, in link
self.langfuse.client.dataset_run_items.create(
File ".venv/lib/python3.11/site-packages/langfuse/api/resources/dataset_run_items/client.py", line 127, in create
raise NotFoundError(pydantic_v1.parse_obj_as(typing.Any, _response.json())) # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
langfuse.api.resources.commons.errors.not_found_error.NotFoundError: status_code: 404, body: {'message': 'Trace not found'}
.../eval.py
Traceback (most recent call last):
File ".../eval.py", line 191, in <module>
main()
File ".../eval.py", line 100, in main
handler = item.get_langchain_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File ".venv/lib/python3.11/site-packages/langfuse/client.py", line 2553, in get_langchain_handler
self.link(
File ".venv/lib/python3.11/site-packages/langfuse/client.py", line 2518, in link
self.langfuse.client.dataset_run_items.create(
File ".venv/lib/python3.11/site-packages/langfuse/api/resources/dataset_run_items/client.py", line 127, in create
raise NotFoundError(pydantic_v1.parse_obj_as(typing.Any, _response.json())) # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
langfuse.api.resources.commons.errors.not_found_error.NotFoundError: status_code: 404, body: {'message': 'Trace not found'}
1 Reply
bjjdjango
bjjdjango4mo ago
Interestingly enough, this only seems to happen in a self-hosted environment... Never mind. Somehow I was stuck on an old version, but the latest version doesn' thave this issue.