文件最后提交记录最后更新时间
feat: 增加同步知识库至DeepSearch功能 Co-authored-by: Mmmmroy<le.zhang1@h-partners.com> # message auto-generated for no-merge-commit merge: !846 feat: 增加同步知识库至DeepSearch功能 From: @Mmmmroy Reviewed-by: @xiaoyao42, @ZYQ5333 See merge request: openJiuwen/agent-studio!8462 个月前
feat(kb): add new kb type weblink for frontend and backend Co-authored-by: Tinaxy<xinyu.hou2@h-partners.com> # message auto-generated for no-merge-commit merge: !813 feat(kb): add new kb type weblink for frontend and backend From: @Tinaxy Reviewed-by: @ZYQ5333, @cyz95, @xiaoyao42 See merge request: openJiuwen/agent-studio!8132 个月前
fix(KB): add DB migration scripts for obs_name column Co-authored-by: Tinaxy<xinyu.hou2@h-partners.com> # message auto-generated for no-merge-commit merge: !773 merge develop-0303 into develop fix(KB): add DB migration scripts for obs_name column Created-by: Tinaxy Commit-by: Tinaxy Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/community/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openjiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- 选择下面一种标签替换下方 /kind <label>,可选标签类型有: - /kind bug - /kind task - /kind feature - /kind refactor - /kind clean_code 如PR描述不符合规范,修改PR描述后需要/check-pr重新检查PR规范。 --> /kind fix **Self-checklist**:(**请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入**) + - [ ] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [ ] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [ ] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [ ] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-studio!7733 个月前
feat: 增加mcp和插件的鉴权 Co-authored-by: wudawei<wudawei6@h-partners.com> # message auto-generated for no-merge-commit merge: !1016 feat: 增加mcp和插件的鉴权 From: @w1101627533 Reviewed-by: @ZYQ5333, @xiaoyao42 See merge request: openJiuwen/agent-studio!10161 个月前
feat: add VLM model management and reports Co-authored-by: yanx1n<yanx1n@noreply.gitcode.com> # message auto-generated for no-merge-commit merge: !998 feat: add VLM model management and reports From: @yanx1n Reviewed-by: @xiaoyao42, @cyz95 See merge request: openJiuwen/agent-studio!9981 个月前
feat: idempotent migrate script modification and fix agent model error Co-authored-by: cs123abc<chensheng63@huawei.com> # message auto-generated for no-merge-commit merge: !653 merge develop-20260210 into develop feat: idempotent migrate script modification and fix agent model error Created-by: chensheng12345 Commit-by: cs123abc Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind refactor **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes # **What scenarios were tested, and what were the verification results(Function, performance, reliability, etc.)**: * Need to describe clearly **Self-checklist**:(**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**) + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [x] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [x] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!6533 个月前
feat: idempotent migrate script modification and fix agent model error Co-authored-by: cs123abc<chensheng63@huawei.com> # message auto-generated for no-merge-commit merge: !653 merge develop-20260210 into develop feat: idempotent migrate script modification and fix agent model error Created-by: chensheng12345 Commit-by: cs123abc Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind refactor **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes # **What scenarios were tested, and what were the verification results(Function, performance, reliability, etc.)**: * Need to describe clearly **Self-checklist**:(**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**) + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [x] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [x] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!6533 个月前
feat: idempotent migrate script modification and fix agent model error Co-authored-by: cs123abc<chensheng63@huawei.com> # message auto-generated for no-merge-commit merge: !653 merge develop-20260210 into develop feat: idempotent migrate script modification and fix agent model error Created-by: chensheng12345 Commit-by: cs123abc Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind refactor **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes # **What scenarios were tested, and what were the verification results(Function, performance, reliability, etc.)**: * Need to describe clearly **Self-checklist**:(**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**) + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [x] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [x] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!6533 个月前
fix : Add idempotent support for unique constraint operations in migrations Co-authored-by: cs123abc<chensheng63@huawei.com> # message auto-generated for no-merge-commit merge: !760 merge develop-20260228-v3 into develop fix : Add idempotent support for unique constraint operations in migrations Created-by: chensheng12345 Commit-by: cs123abc Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind fix **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes # **What scenarios were tested, and what were the verification results(Function, performance, reliability, etc.)**: * Need to describe clearly **Self-checklist**:(**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**) + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [x] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [x] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!7603 个月前
feat: idempotent migrate script modification and fix agent model error Co-authored-by: cs123abc<chensheng63@huawei.com> # message auto-generated for no-merge-commit merge: !653 merge develop-20260210 into develop feat: idempotent migrate script modification and fix agent model error Created-by: chensheng12345 Commit-by: cs123abc Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind refactor **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes # **What scenarios were tested, and what were the verification results(Function, performance, reliability, etc.)**: * Need to describe clearly **Self-checklist**:(**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**) + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [x] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [x] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!6533 个月前
fix: 创建weblink知识库导致知识库列表页面空白 Co-authored-by: Mmmmroy<le.zhang1@h-partners.com> # message auto-generated for no-merge-commit merge: !1046 merge fix/weblink_table into develop fix: 创建weblink知识库导致知识库列表页面空白 Created-by: Mmmmroy Commit-by: Mmmmroy Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/community/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openjiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- 选择下面一种标签替换下方 /kind <label>,可选标签类型有: - /kind bug - /kind task - /kind feature - /kind refactor - /kind clean_code 如PR描述不符合规范,修改PR描述后需要/check-pr重新检查PR规范。 --> /kind bug **Self-checklist**:(**请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入**) + - [ ] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [ ] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [ ] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [ ] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [ ] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-studio!104622 天前