feat: add FastAPI lifespan and healthcheck endpoint

[paul-paliychuk]

Important

Add FastAPI lifespan for graphiti initialization, a /healthcheck endpoint, and initialize_graphiti function for index setup.

• FastAPI Lifespan: Added lifespan async context manager in main.py for graphiti initialization.
• Endpoints: Replaced root endpoint with /healthcheck in main.py, returning JSON status.
• Graphiti Initialization: Added initialize_graphiti() in zep_graphiti.py for index and constraint setup.

^{This description was created by for f651132. It will automatically update as commits are pushed.}

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to cd3906d in 14 seconds

More details

• Looked at 57 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. server/graph_service/zep_graphiti.py:85

• Draft comment:
  The initialize_graphiti and get_graphiti functions have repetitive code for creating a ZepGraphiti client. Consider refactoring to avoid this repetition and adhere to the DRY principle.
• Reason this comment was not posted:
  Confidence changes required: 80%
  The code in initialize_graphiti and get_graphiti is very similar, violating the DRY principle. They both create a ZepGraphiti client with the same parameters. This should be refactored to avoid repetition.

2. server/graph_service/main.py:1

• Draft comment:
  Ensure a copyright notice is present at the top of this file and other Python files in the project.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_pOUGiWDGYAwGShI5

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on f651132 in 15 seconds

More details

• Looked at 28 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. server/graph_service/main.py:17

• Draft comment:
  Ensure that Graphiti is properly closed after each request to prevent resource leaks. The comment suggests this is handled per-request, but it's not evident in the code.
• Reason this comment was not posted:
  Confidence changes required: 80%
  The lifespan function initializes Graphiti but does not handle its closure. This could lead to resource leaks if Graphiti is not closed properly after each request. The comment suggests that closure is handled per-request, but this is not evident in the code provided.

2. server/graph_service/main.py:14

• Draft comment:
  The function initialize_graphiti is performing multiple tasks related to index setup. Consider breaking it down into smaller functions to adhere to the Single Responsibility Principle.
• Reason this comment was not posted:
  Confidence changes required: 80%
  The code in graphiti.py and main.py is mostly well-structured, but there are some issues to address.

3. graphiti_core/graphiti.py:158

• Draft comment:
  The comment block for the close method is extensive. Consider making it more concise while retaining essential information.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The code in graphiti.py and main.py is mostly well-structured, but there are some issues to address.

Workflow ID: wflow_xijkjjhsyULfuLi7

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.