Merge jiuwenclaw - #18
Open
CharlieZhao95 wants to merge 18 commits into
Open
Conversation
Co-authored-by: hewenli<hewenli1@huawei.com> # message auto-generated for no-merge-commit merge: !173 feat: 企业微信对接文档 From: @xiaowenzihwl Reviewed-by: @douran, @shiruifeng1116, @xinyu-jiuwen, @hy592070616 See merge request: openJiuwen/jiuwenclaw!173
Co-authored-by: huanggawa<huangjiahua6@huawei.com> Co-authored-by: douran<douran1@huawei.com> # message auto-generated for no-merge-commit merge: !170 fix: 版本升级适配配置与技能迁移 From: @huanggawa Reviewed-by: @xinyu-jiuwen, @shiruifeng1116, @douran See merge request: openJiuwen/jiuwenclaw!170
Co-authored-by: shiruifeng1116<shiruifeng@huawei.com> # message auto-generated for no-merge-commit merge: !174 merge revert-mr-170-1774273542631-auto into develop fix: 解决升级config与记忆迁移 Created-by: shiruifeng1116 Commit-by: shiruifeng1116 Merged-by: iamcandiceguo 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 <label> **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/jiuwenclaw!174
Co-authored-by: ray_le<lilei336@huawei.com> # message auto-generated for no-merge-commit merge: !177 merge develop into develop fix: 飞书流式问题回退 Created-by: ray_le Commit-by: ray_le Merged-by: iamcandiceguo 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 <label> **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/jiuwenclaw!177
Co-authored-by: ray_le<lilei336@huawei.com> # message auto-generated for no-merge-commit merge: !178 merge develop into develop fix: feishu 提前结束问题修复 Created-by: ray_le Commit-by: ray_le Merged-by: zhuxushen 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 <label> **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/jiuwenclaw!178
Co-authored-by: ray_le<lilei336@huawei.com> # message auto-generated for no-merge-commit merge: !179 feat: readme update by version 0.1.7 From: @ray_le Reviewed-by: @douran, @xinyu-jiuwen, @shiruifeng1116 See merge request: openJiuwen/jiuwenclaw!179
Co-authored-by: ray_le<lilei336@huawei.com> # message auto-generated for no-merge-commit merge: !181 fix: core patch bugfix revert From: @ray_le Reviewed-by: @shiruifeng1116, @douran See merge request: openJiuwen/jiuwenclaw!181
Co-authored-by: huanggawa<huangjiahua6@huawei.com> # message auto-generated for no-merge-commit merge: !185 fix: remove ci workflow From: @huanggawa Reviewed-by: @douran, @shiruifeng1116 See merge request: openJiuwen/jiuwenclaw!185
Co-authored-by: ray_le<lilei336@huawei.com> # message auto-generated for no-merge-commit merge: !186 fix: channel下不同session信息错乱问题修复 From: @ray_le Reviewed-by: @shiruifeng1116, @xinyu-jiuwen, @douran See merge request: openJiuwen/jiuwenclaw!186
Co-authored-by: shenwei21<ultrarelax@163.com> # message auto-generated for no-merge-commit merge: !180 feat: 小艺channel支持端插件tool（小艺claw场景），并预置位置、备忘录等11个端插件tools From: @shenwei21 Reviewed-by: @douran, @hy592070616 See merge request: openJiuwen/jiuwenclaw!180
Co-authored-by: Haowei_Du<duhaowei1@huawei.com> # message auto-generated for no-merge-commit merge: !175 feat: 提供cron openclaw和jiuwenclaw的转换脚本 From: @Haowei_Du Reviewed-by: @douran, @xinyu-jiuwen, @shiruifeng1116 See merge request: openJiuwen/jiuwenclaw!175
Co-authored-by: jingjinduo<jingjinduo@huawei.com> # message auto-generated for no-merge-commit merge: !182 feat: 支持向小艺claw更新使用工具的状态 From: @jingjinduo Reviewed-by: @douran, @shiruifeng1116 See merge request: openJiuwen/jiuwenclaw!182
Co-authored-by: huanggawa<huangjiahua6@huawei.com> # message auto-generated for no-merge-commit merge: !191 fix: readme typo From: @huanggawa Reviewed-by: @shiruifeng1116, @douran See merge request: openJiuwen/jiuwenclaw!191
Co-authored-by: bhyeo<yeo.boon.hong@huawei.com> # message auto-generated for no-merge-commit merge: !188 feat: Add Experience Retrieve and Experience Learn Tools From: @bhyeo Reviewed-by: @douran, @shiruifeng1116 See merge request: openJiuwen/jiuwenclaw!188
…n_history 方法. 返回历史消息和总页数 3. gateway提供history.get，调用agent server定义的方法，将返回的内容流式返回，每条历史消息发一个事件 Co-authored-by: Haowei_Du<duhaowei1@huawei.com> # message auto-generated for no-merge-commit merge: !192 feat: 1. interface所有接收的输入，产生的输出落盘 2. agent_server 里添加 get_conversation_history 方法. 返回历史消息和总页数 3. gateway提供history.get，调用agent server定义的方法，将返回的内容流式返回，每条历史消息发一个事件 From: @Haowei_Du Reviewed-by: @hy592070616, @douran See merge request: openJiuwen/jiuwenclaw!192
Co-authored-by: NickFuryXXX<huhuanran2@huawei.com> # message auto-generated for no-merge-commit merge: !196 feat: 前端支持会话恢复，端到端联调完成 From: @NickFuryXXX Reviewed-by: @hy592070616, @douran See merge request: openJiuwen/jiuwenclaw!196
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.