Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ragKnowledge): Ensure scoped IDs are properly used to check for existing knowledge #2690

Merged
merged 5 commits into from
Jan 23, 2025

Conversation

augchan42
Copy link
Contributor

fix(ragKnowledge): Ensure scoped IDs are properly used to check for existing knowledge

  • Updated logic to correctly handle scoped IDs when verifying existing knowledge entries.
  • Improved validation to prevent issues with knowledge retrieval and management.

The problem is in how knowledge IDs are handled between checking for existence and creation.

  1. In processCharacterRAGKnowledge, you generate the ID using:
const knowledgeId = stringToUuid(contentItem);  // contentItem is the file path
  1. But in RAGKnowledgeManager.processFile, you generate the ID using:
const scopedId = this.generateScopedId(file.path, file.isShared || false);

The mismatch is here - when you check for existing knowledge using getKnowledge, you're using the first ID generation method (just based on file path), but when you actually create the knowledge, you're using the second method (which includes the scope prefix).

This means:

  • Check for existence using: stringToUuid("shared/warringstates/zhibo.md")
  • Actually stored with: stringToUuid("shared-shared/warringstates/zhibo.md")

The fix would be to use the same ID generation method in both places. You should modify processCharacterRAGKnowledge to use generateScopedId when checking for existence:

// In processCharacterRAGKnowledge
const knowledgeId = this.ragKnowledgeManager.generateScopedId(contentItem, isShared);

Fixes #2689

Copy link
Contributor

coderabbitai bot commented Jan 23, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@wtfsayo wtfsayo added this pull request to the merge queue Jan 23, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Jan 23, 2025
@wtfsayo wtfsayo added this pull request to the merge queue Jan 23, 2025
@wtfsayo wtfsayo merged commit 02f6114 into elizaOS:develop Jan 23, 2025
7 checks passed
VonLuderitz pushed a commit to VonLuderitz/eliza that referenced this pull request Feb 19, 2025
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.

bug: ragKnowledge doesn't properly check for scoped Ids for existing knowledge
3 participants