Skip to content

fix: crewai examples, bump dependencies - #421

Merged
paul-paliychuk merged 2 commits into
mainfrom
fix-crew-ai-examples
Aug 25, 2025
Merged

paul-paliychuk merged 2 commits into
mainfrom
fix-crew-ai-examples

Conversation

@paul-paliychuk

@paul-paliychuk paul-paliychuk commented Aug 25, 2025

Copy link
Copy Markdown
Collaborator

Important

Fix CrewAI examples, update dependencies, and improve error handling in search methods.

  • Examples:
    • crewai_graph.py: Add zep_client.graph.create() for graph initialization and update set_ontology() to use graph_ids list.
    • crewai_tools.py: Simplify user creation by removing exception handling for existing users.
    • crewai_user.py: Update user creation to handle existing users more gracefully.
  • Dependencies:
    • Update zep-cloud to >=3.4.1 in pyproject.toml.
    • Bump version to 1.0.0 in pyproject.toml.
  • Source Code:
    • graph_storage.py and user_storage.py: Add error handling in search() methods.
    • Change context to memory in search results.
  • Tests:
    • Update test_graph_storage.py and test_user_storage.py to reflect changes in search result keys.
  • Misc:
    • Update README to change "data indexing" to "data processing".

This description was created by Ellipsis for 84662e0. You can customize this summary. It will automatically update as commits are pushed.

@ellipsis-dev ellipsis-dev Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed everything up to 5d136bd in 2 minutes and 31 seconds. Click for details.
  • Reviewed 274 lines of code in 8 files
  • Skipped 0 files when reviewing.
  • Skipped posting 11 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. integrations/python/zep_crewai/examples/crewai_graph.py:16
  • Draft comment:
    Importing 'SearchFilters' improves type safety for search filters.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative and does not provide any actionable feedback or suggestions for improvement. It simply states a fact about the code change without offering any guidance or questions for the PR author.
2. integrations/python/zep_crewai/examples/crewai_graph.py:57
  • Draft comment:
    Explicitly creating the graph before setting the ontology ensures the graph exists as expected.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative and does not provide any actionable feedback or suggestions for improvement. It simply states what the code is doing without offering any critique or advice.
3. integrations/python/zep_crewai/examples/crewai_graph.py:66
  • Draft comment:
    Updated ontology setup: using 'graph_ids' as a list aligns with the expected API contract. Verify that this change is compatible with the underlying API.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to verify compatibility with the underlying API, which violates the rule against asking for confirmation or verification of intentions. It does not provide a specific suggestion or point out a clear issue.
4. integrations/python/zep_crewai/examples/crewai_graph.py:81
  • Draft comment:
    Using a SearchFilters instance (instead of a raw dict) for search_filters enhances validation and clarity.
  • Reason this comment was not posted:
    Comment looked like it was already resolved.
5. integrations/python/zep_crewai/examples/crewai_tools.py:40
  • Draft comment:
    User creation was simplified by removing duplicate handling. Ensure that duplicate users (if already existing) are managed appropriately by the Zep API.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 50% <= threshold 50% The comment is asking the author to ensure that duplicate users are managed appropriately by the Zep API. This is a request for confirmation of behavior, which violates the rule against asking the author to ensure behavior is intended. However, it does point out a potential issue with duplicate handling, which could be useful.
6. integrations/python/zep_crewai/pyproject.toml:3
  • Draft comment:
    Bumped version to 1.0.0 and updated the zep-cloud dependency to >=3.4.1. Ensure this aligns with the release notes and backward compatibility.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is about a version bump and dependency update, which falls under the rule of not commenting on pure dependency changes. The suggestion to ensure alignment with release notes and backward compatibility is also a form of asking the author to double-check things, which is not allowed.
7. integrations/python/zep_crewai/src/zep_crewai/graph_storage.py:115
  • Draft comment:
    The search method now wraps its operations in a try/except block and returns results with a 'memory' key (instead of 'context'), which improves error handling and consistency.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, describing changes made to the code without suggesting any improvements or asking for clarification. It doesn't align with the rules for useful comments.
8. integrations/python/zep_crewai/src/zep_crewai/tools.py:170
  • Draft comment:
    Enhanced search tool result formatting now prioritizes the 'memory' field (with fallbacks to 'context' and 'content'), which aids compatibility with updated storage return values.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining the changes made to the search tool result formatting. It doesn't provide any actionable feedback or suggestions for improvement.
9. integrations/python/zep_crewai/src/zep_crewai/user_storage.py:157
  • Draft comment:
    User storage search now returns a result with the 'memory' key, ensuring consistency with the graph storage changes.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, describing a change without providing any actionable feedback or suggestions. It doesn't ask for confirmation or suggest improvements.
10. integrations/python/zep_crewai/tests/test_graph_storage.py:128
  • Draft comment:
    Test updated to assert on the 'memory' field (instead of 'context'), which aligns with the refactored search method.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining what was changed in the test. It doesn't provide a suggestion, ask for confirmation, or point out a potential issue. According to the rules, purely informative comments should be removed.
11. integrations/python/zep_crewai/tests/test_user_storage.py:134
  • Draft comment:
    Tests for user storage have been updated to assert on the 'memory' key in search results, ensuring consistency with the updated implementation.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_GjDvBdlz94WVCo6j

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@ellipsis-dev ellipsis-dev Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed 84662e0 in 1 minute and 3 seconds. Click for details.
  • Reviewed 68 lines of code in 5 files
  • Skipped 0 files when reviewing.
  • Skipped posting 5 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. integrations/python/zep_crewai/README.md:362
  • Draft comment:
    Updated to 'data processing'; ensure consistency with backend terminology.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
2. integrations/python/zep_crewai/examples/crewai_graph.py:142
  • Draft comment:
    Revised wait message to 'data processing' for consistency.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
3. integrations/python/zep_crewai/examples/crewai_tools.py:142
  • Draft comment:
    Changed wait message to 'data processing'; looks consistent.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
4. integrations/python/zep_crewai/examples/crewai_user.py:146
  • Draft comment:
    Updated wait message to 'data processing' for uniformity.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
5. integrations/python/zep_crewai/src/zep_crewai/tools.py:169
  • Draft comment:
    Direct lookup of 'content' and 'created_at' without fallback; ensure these keys are always present.
  • Reason this comment was not posted:
    Confidence changes required: 50% <= threshold 50% None

Workflow ID: wflow_ZNkUcDEXArgwj7Ja

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@paul-paliychuk
paul-paliychuk merged commit 40bf779 into main Aug 25, 2025
9 checks passed
@paul-paliychuk
paul-paliychuk deleted the fix-crew-ai-examples branch August 25, 2025 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant