Skip to content

Conversation

@dingyi222666
Copy link
Member

This PR bumps the version of chatluna and its packages to 1.3.6.

New Features

  • None

Bug fixes

  • None

Other Changes

  • Updated package versions and peer dependencies.
  • Commented out validation logic in packages/service-vector-store/src/vectorstore/base/lunavdb.ts.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 23, 2025

Caution

Review failed

The pull request is closed.

总体概述

在 LunaDBVectorStore.delete 方法中移除了运行时验证逻辑。之前的实现会检查请求的 ID 是否存在,现在跳过了这些检查,直接对提供的 ID 进行删除操作。

变更内容

分组 / 文件 变更摘要
运行时验证移除
packages/service-vector-store/src/vectorstore/base/lunavdb.ts
注释掉映射 ID 加载、缺失 ID 计算和错误抛出逻辑。删除操作现在跳过存在性检查,直接从内存文档存储中删除提供的 ID 并执行客户端移除。

代码审查工作量估估

🎯 2 (简单) | ⏱️ ~8 分钟

庆祝诗

🐰 验证去,删除来,
注释掉烦恼之害,
直接删除无需等,
效率提升是本怀,
代码轻盈向前跃!✨

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/bump-version

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2dbb733 and 0fe0c5a.

⛔ Files ignored due to path filters (26)
  • packages/adapter-azure-openai/package.json is excluded by !**/*.json
  • packages/adapter-claude/package.json is excluded by !**/*.json
  • packages/adapter-deepseek/package.json is excluded by !**/*.json
  • packages/adapter-dify/package.json is excluded by !**/*.json
  • packages/adapter-doubao/package.json is excluded by !**/*.json
  • packages/adapter-gemini/package.json is excluded by !**/*.json
  • packages/adapter-hunyuan/package.json is excluded by !**/*.json
  • packages/adapter-ollama/package.json is excluded by !**/*.json
  • packages/adapter-openai-like/package.json is excluded by !**/*.json
  • packages/adapter-openai/package.json is excluded by !**/*.json
  • packages/adapter-qwen/package.json is excluded by !**/*.json
  • packages/adapter-rwkv/package.json is excluded by !**/*.json
  • packages/adapter-spark/package.json is excluded by !**/*.json
  • packages/adapter-wenxin/package.json is excluded by !**/*.json
  • packages/adapter-zhipu/package.json is excluded by !**/*.json
  • packages/core/package.json is excluded by !**/*.json
  • packages/extension-long-memory/package.json is excluded by !**/*.json
  • packages/extension-mcp/package.json is excluded by !**/*.json
  • packages/extension-tools/package.json is excluded by !**/*.json
  • packages/extension-variable/package.json is excluded by !**/*.json
  • packages/renderer-image/package.json is excluded by !**/*.json
  • packages/service-embeddings/package.json is excluded by !**/*.json
  • packages/service-image/package.json is excluded by !**/*.json
  • packages/service-search/package.json is excluded by !**/*.json
  • packages/service-vector-store/package.json is excluded by !**/*.json
  • packages/shared-adapter/package.json is excluded by !**/*.json
📒 Files selected for processing (1)
  • packages/service-vector-store/src/vectorstore/base/lunavdb.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@dingyi222666 dingyi222666 merged commit a0de752 into v1-dev Dec 23, 2025
2 of 3 checks passed
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @dingyi222666, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on a routine version update, bumping the chatluna ecosystem to version 1.3.6. This involves updating the version numbers of the main package and its numerous adapters and extensions, along with their respective peer dependencies. Additionally, a specific validation check within the vector store service was temporarily disabled.

Highlights

  • Version Bump: The core chatluna package and all its associated sub-packages and adapters have been updated to version 1.3.6.
  • Dependency Updates: All package.json files across the various packages have had their koishi-plugin-chatluna peer dependency updated to ^1.3.6 to reflect the new core version.
  • Vector Store Logic Change: Validation logic in packages/service-vector-store/src/vectorstore/base/lunavdb.ts that checked for missing document IDs during deletion has been commented out.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request primarily consists of version bumps for a new release, which is standard procedure. However, I have a significant concern about the change in packages/service-vector-store/src/vectorstore/base/lunavdb.ts, where validation logic for document deletion has been commented out. This change silences errors when attempting to delete non-existent documents, which can hide bugs and make debugging more difficult. I've added a detailed comment explaining my concerns and providing an example of how to restore the safer behavior.

Comment on lines +140 to +142
// const mappingIds = Array.from(this.docstore._docs.keys())

const missingIds = documentIds.filter((id) => !mappingIds.includes(id))

if (missingIds.length > 0) {
throw new Error(
`Some specified documentIds do not exist in the current store. DocumentIds not found: ${Array.from(
missingIds
).join(', ')}`
)
}
// const missingIds = documentIds.filter((id) => !mappingIds.includes(id))
Copy link
Contributor

Choose a reason for hiding this comment

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

high

Commenting out this validation logic makes the delete operation more lenient, but it also introduces risks by hiding potential bugs. If a caller attempts to delete a document ID that doesn't exist, the operation will now silently pass, whereas before it would throw an error. This can mask problems in the calling logic and lead to a difficult-to-debug inconsistent state.

I recommend re-instating the validation that throws an error for non-existent IDs. If making the deletion idempotent is a requirement, a safer approach would be to explicitly check for existence and log a warning for missing IDs instead of throwing an error. Simply removing the check is risky.

For example, you could restore the previous logic:

const mappingIds = Array.from(this.docstore._docs.keys())

const missingIds = documentIds.filter((id) => !mappingIds.includes(id))

if (missingIds.length > 0) {
    throw new Error(
        `Some specified documentIds do not exist in the current store. DocumentIds not found: ${Array.from(
            missingIds
        ).join(', ')}`
    )
}

@dingyi222666 dingyi222666 deleted the chore/bump-version branch December 25, 2025 16:54
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.

2 participants