memU icon indicating copy to clipboard operation
memU copied to clipboard

Issue when running `retrieve_default_categories`

Open yiweizh-memverge opened this issue 4 months ago • 3 comments

Hi,

I am trying out your example client-side program with other conversations. The conversation format follows the format of the example conversation.json. But after I ran the memorize_conversation and confirmed the task finished successfully, and later proceeded to retrieve_default_categories, it is giving the following errors:

Traceback (most recent call last):
  File "/memverge/home/yiweiz/miniconda3/lib/python3.13/site-packages/memu/sdk/python/client.py", line 331, in retrieve_default_categories
    response = DefaultCategoriesResponse(**response_data)
  File "/memverge/home/yiweiz/miniconda3/lib/python3.13/site-packages/pydantic/main.py", line 214, in __init__
    validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self)
pydantic_core._pydantic_core.ValidationError: 16 validation errors for DefaultCategoriesResponse
categories.0.memories.0.created_at
  Input should be a valid datetime [type=datetime_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.10/v/datetime_type
categories.0.memories.0.updated_at
  Input should be a valid datetime [type=datetime_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.10/v/datetime_type
categories.0.memories.1.created_at
  Input should be a valid datetime [type=datetime_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.10/v/datetime_type
categories.0.memories.1.updated_at
  Input should be a valid datetime [type=datetime_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.10/v/datetime_type
categories.1.memories.0.created_at
  Input should be a valid datetime [type=datetime_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.10/v/datetime_type
categories.1.memories.0.updated_at
  Input should be a valid datetime [type=datetime_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.10/v/datetime_type
categories.1.memories.1.created_at
  Input should be a valid datetime [type=datetime_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.10/v/datetime_type
categories.1.memories.1.updated_at

yiweizh-memverge avatar Aug 14 '25 19:08 yiweizh-memverge

I'm sorry that this may be caused by a temporary error in our server or database, which let

  • The server fail to fetch the created_at and updated_at values from the database;
  • Return None to the client;
  • Cause a data validation error in the SDK

We are considering either adding stricter validation on our server or relaxing the validation in the SDK (allowing created_at and updated_at to be None). Has this problem happened only once, or can it be consistently reproduced in your environment?

evan-ak avatar Aug 15 '25 15:08 evan-ak

Hi,

Yes, it is a consistently reproducible problem. I can try with a new user_id and go through the process of memorization and retrieval again. Regarding the temporary error you mentioned, is there any plan to fix it?

Thanks!

yiweizh-memverge avatar Aug 18 '25 17:08 yiweizh-memverge

I am having exactly the same issue here. I have created new conversations multiple times, and it still fails in every one of them.

BritishTeapot avatar Aug 29 '25 11:08 BritishTeapot