Title: graphiti-mcp-server Docker container hangs at 100% CPU when processing updates/corrections via add_episode

[danielchalef (maintainer)]: Closing as #512 has been merged. If this issue impacted you, please pull from main and rebuild your container.

Context: GitHub issue getzep/graphiti#450 (closed, 13 comments): Description The graphiti-mcp-server, when run via the provided docker-compose.yml, consistently enters an unresponsive state with 100% CPU utilization after processing an addepisode call that updates or corrects information about a recently added entity. Adding completely new, unrelated information seems to work fine, but modifying existing facts reliably triggers the hang. To Reproduce Steps to reproduce the behavior: 1. Start the graphiti-mcp-server using docker compose -f mcpserver/docker-compose.yml up -d (using the files from the getzep/graphiti repo). 2. Use the add_episode too

GitHub issue getzep/graphiti#450 (closed, 13 comments): Description The graphiti-mcp-server, when run via the provided docker-compose.yml, consistently enters an unresponsive state with 100% CPU utilization after processing an addepisode call that updates or corrects information about a recently added entity. Adding completely new, unrelated information seems to work fine, but modifying existing facts reliably triggers the hang. To Reproduce Steps to reproduce the behavior: 1. Start the graphiti-mcp-server using docker compose -f mcpserver/docker-compose.yml up -d (using the files from the getzep/graphiti repo). 2. Use the add_episode too Verified answer: [danielchalef (maintainer)]: Closing as #512 has been merged. If this issue impacted you, please pull from main and rebuild your container. Source: https://github.com/getzep/graphiti/issues/450