feat: Fix bug in dedupe_node_list function

[danielchalef]

The code changes fix a bug in the dedupe_node_list function where a node instance was not found in the node map. The bug is now handled by logging a warning message and skipping the iteration. This ensures that the function continues to execute without any errors.

---

Important

Fixes bug in dedupe_node_list by handling missing node instances with a warning and skipping iteration.

• Bug Fix:
  • In dedupe_node_list function, handle missing node instances in node_map by logging a warning and skipping the iteration.
  • Ensures function execution continues without errors when a node is not found.

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

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 1544425 in 15 seconds

More details

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

1. graphiti_core/utils/maintenance/node_operations.py:283

• Draft comment:
  Use node_instance.uuid instead of node_map[node_data['uuids'][0]].uuid to avoid potential KeyError.

            uuid_value = node_instance.uuid

• Reason this comment was not posted:
  Comment was on unchanged code.

2. graphiti_core/utils/maintenance/node_operations.py:272

• Draft comment:
  The context preparation logic for LLM is repeated in extract_message_nodes, extract_text_nodes, and extract_json_nodes. Consider refactoring this into a separate function to adhere to the DRY principle.
• Reason this comment was not posted:
  Confidence changes required: 80%
  The code has repetitive logic for preparing context for LLM in multiple functions. This violates the DRY principle.

Workflow ID: wflow_7coLru3tURpmy06p

---

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.