Catch classification exceptions

[prasmussen15]

Important

Add exception handling for node classification errors in extract_nodes and update version to 0.7.6.

• Behavior:
  • Add exception handling in extract_nodes in node_operations.py to catch and log errors during node classification.
• Versioning:
  • Update version in pyproject.toml from 0.7.5 to 0.7.6.

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

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 52deb74 in 1 minute and 27 seconds

More details

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

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

• Draft comment:
  The try/finally block here does not catch exceptions as intended. Use try/except to catch errors and log them in the except block instead of finally, which always executes.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_XXHjBs2tshAKyTS8

---

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]

❌ Changes requested. Incremental review on 989ac7c in 1 minute and 20 seconds

More details

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

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

• Draft comment:
  Good change catching exceptions in node classification. Consider using logger.exception (or logger.error with exc_info=True) to log the full traceback for easier debugging.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_2WMMI8myDRLD0fM2

---

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.