Memory tool problems

[christos-chatzifountas-biotz-io]

Memory tool unable to save and restore memories.
After experiencing this problem, i asked agent to
"test save and restore memory

Agent 0: Starting a message:
{
    "thoughts": [
        "The attempt to restore the memory using the new saved ID also did not yield any results.",
        "This indicates a persistent issue with the memory saving and restoring functionality.",
        "I will now check if there are any specific errors or limitations regarding memory management."
    ],
    "tool_name": "knowledge_tool",
    "tool_args": {
        "question": "What are the limitations or issues with memory management in the current system?"
    }
}

Agent 0: Using tool 'knowledge_tool':
Question: What are the limitations or issues with memory management in the current system?

Generally, after many attempts, i was able to save and retrieve 2 memory ids and only too. Old memories are there if i checkout to previous commit.

This is the final agent messaging:

Agent 0: Starting a message:
{
    "thoughts": [
        "The attempt to restore the memory using the latest saved ID also did not yield any results.",
        "This confirms that there is a significant issue with the memory management system, as saving and restoring functionalities are not working as expected.",
        "I will now summarize the findings and prepare a report regarding the memory management issues encountered."
    ],
    "tool_name": "response",
    "tool_args": {
        "text": "The investigation into the memory management system revealed persistent issues with saving and restoring functionalities. Despite successfully saving multiple test memories, attempts to restore them consistently returned 'No memories found' for the specified IDs. This indicates a critical flaw in the memory management system that needs to be addressed."
    }
}

Agent 0: reponse:
The investigation into the memory management system revealed persistent issues with saving and restoring functionalities. Despite successfully saving multiple test memories, attempts to restore them consistently returned 'No memories found' for the specified IDs. This indicates a critical flaw in the memory management system that needs to be addressed.

[ZanBlayde]

I did what you said and told it to test and save a couple memories. It got some errors along the way but was able to save them. I asked it to tell me what errors it received before being able to save its first memory and it gave me this:

When trying to save the first memory, the following validation error occurred:

Traceback (most recent call last):
  File "/opt/miniconda3/envs/agent_zero/lib/python3.10/site-packages/langchain_core/load/serializable.py", line 113, in __init__
    super().__init__(*args, **kwargs)
  File "/opt/miniconda3/envs/agent_zero/lib/python3.10/site-packages/pydantic/v1/main.py", line 341, in __init__
    raise validation_error
pydantic.v1.error_wrappers.ValidationError: 1 validation error for Document
page_content
  str type expected (type=type_error.str)

This error indicated that the 'page_content' field needed to be a string. After adjusting the format to ensure it was a single string, the memory was successfully saved.`

[christos-chatzifountas-biotz-io]

I dont understand the code adjustment i have to make to make it work. I am not good with python