| fix:前端弹框编辑后退出前需要确认 Co-authored-by: wangxin<wangxin375@huawei.com> # message auto-generated for no-merge-commit merge: !490 merge develop into develop fix:前端弹框编辑后退出前需要确认 Created-by: programmegirl Commit-by: wangxin Merged-by: cyz95 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!490 | 4 小时前 |
| fix: 打通用户面的同源代理并补齐联合认证配置 Co-authored-by: whq<whqxbs@163.com> # message auto-generated for no-merge-commit merge: !463 merge fix/manager-web-gateway-transport into develop fix: 打通用户面的同源代理并补齐联合认证配置 Created-by: u010240195 Commit-by: whq Merged-by: cyz95 Description: Paired: [GitHub #112](https://github.com/openJiuwen-ai/agent-runtime/pull/112) ↔ [GitCode !463](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/463) <!-- 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**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 463 github_repo: openJiuwen-ai/agent-runtime github_pr: 112 github_branch: sync/pr-463 --> See merge request: openJiuwen/agent-runtime!463 | 6 天前 |
| docs: 文档重构支持项目记忆管理。文档三分重组——design/spec/feature 下沉模块根,spec 按子包拆分 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !439 merge develop1 into develop docs: 文档重构支持项目记忆管理。文档三分重组——design/spec/feature 下沉模块根,spec 按子包拆分 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: cyz95 Description: Paired: [GitHub #87](https://github.com/openJiuwen-ai/agent-runtime/pull/87) ↔ [GitCode !439](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/439) <!-- 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**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 439 github_repo: openJiuwen-ai/agent-runtime github_pr: 87 github_branch: sync/pr-439 --> See merge request: openJiuwen/agent-runtime!439 | 10 天前 |
| 支持数据库分实例隔离数据 Co-authored-by: chen hui<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !472 merge support-db-instance-isolation into develop 支持数据库分实例隔离数据 Created-by: chen-hui-zhe-xi Commit-by: chen hui Merged-by: ZYQ5333 Description: Paired: [GitHub #121](https://github.com/openJiuwen-ai/agent-runtime/pull/121) ↔ [GitCode !472](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/472) <!-- 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 feature **Self-checklist**:(**请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 472 github_repo: openJiuwen-ai/agent-runtime github_pr: 121 github_branch: sync/pr-472 --> See merge request: openJiuwen/agent-runtime!472 | 4 天前 |
| fix agentserver boot issue Co-authored-by: chen hui<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !448 merge fix-agentserver-boot-issue into develop fix agentserver boot issue Created-by: chen-hui-zhe-xi Commit-by: chen hui Merged-by: cyz95 Description: Paired: [GitHub #97](https://github.com/openJiuwen-ai/agent-runtime/pull/97) ↔ [GitCode !448](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/448) <!-- 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**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 448 github_repo: openJiuwen-ai/agent-runtime github_pr: 97 github_branch: sync/pr-448 --> See merge request: openJiuwen/agent-runtime!448 | 9 天前 |
| agent-runtime 分布式服务首提交 docs(e2e): 新增端到端测试用例说明——全部场景/输入/预期输出逐条化 docs/e2e-test-cases.md: - 四层体系总览(双实例 pytest / M6 冒烟 65 项 / 多副本 e2e 35 项 / 压测) 与退出码约定 - 通用约定:请求信封格式、错误码契约表、Redis 真相源键、前置自检与 FLUSHDB 防误刷语义 - M6 冒烟:模板矩阵 + 13 阶段 52 条用例逐条(场景映射/输入/预期) - 多副本 e2e:S0–S8 逐条(含 DEGRADED 语义、failover 目标选择、 winner∈candidates 互斥不变量) - 双实例 12 用例与压测 3 场景的输入/判定 - 环境与重现手册(Redis DB1/DB2 约定、集群部署、逐层命令) - 已知语义差异(多副本冷突发 NO_POD_AVAILABLE、冷竞争双 Pod 自愈、 场景 N 暂缓、config_sync 串行) README/code-guide §7/CLAUDE.md 增交叉引用 Co-Authored-By: Claude <noreply@anthropic.com> fix(e2e): 经多副本 LB 跑 M6 冒烟 63/65 的根因修复——65/65 两处失败初判「多副本冷突发语义」,排查证明均为部署配置差异: 1. F-队列超时 504 缺失:集群部署漏设 AGENT_RUNTIME_SCOPE_FULL_TIMEOUT (默认 30s 恰等于 tpl-f session_ttl=30s)→ 等待者 deadline≈会话到期, 被到期驱逐的 PUBLISH 提前唤醒 → 竞态窗口内 2×NO_POD_AVAILABLE+ 2×200 混合、无干净 504。修复:部署模板补该变量(默认 8,红线注释 「须显著小于 session_ttl」)+ env.example。 2. cleanup 空目标 500:admin 凭据对不存在 ns list 得空列表,in-cluster SA 的 namespaced RBAC 先行 403 → ApiException 未处理裸 500(4/4 稳定 复现)。修复:产品 cleanup 对 404 容忍为 cleaned=0(跨凭据形态行为 对齐),403 保持 fail-fast(静默清零会掩盖 RBAC 配错);+2 单测。 测试空目标改用无匹配 label_selector——期间实测踩坑:业务 ns 会误删 同 label 真实 AgentServer(default ns 2 个 gateway 管理的 Pod 被误删, 其一 16s 自愈,handoff §十一.6 教训再现);min_idle 热备 1s 重建致 刚清空的 ns 也不为空。三坑实录入 docs/e2e-test-cases.md §8.1。 验证:M6 冒烟经 LB 65/65 + 单实例 65/65;多副本 e2e 35/35; pytest 104→106 全绿。文档计数与归因同步(CLAUDE/README/code-guide/ handoff §十一.1 补记)。 Co-Authored-By: Claude <noreply@anthropic.com> | 15 天前 |
| refactor(observability): 诊断端点 /debug → /visualization——对外去敏感化,行为零变化 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !473 merge develop into develop refactor(observability): 诊断端点 /debug → /visualization——对外去敏感化,行为零变化 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: ZYQ5333 Description: Paired: [GitHub #122](https://github.com/openJiuwen-ai/agent-runtime/pull/122) ↔ [GitCode !473](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/473) <!-- 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**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 473 github_repo: openJiuwen-ai/agent-runtime github_pr: 122 github_branch: sync/pr-473 --> See merge request: openJiuwen/agent-runtime!473 | 3 天前 |
| agent-runtime 分布式服务首提交 docs(e2e): 新增端到端测试用例说明——全部场景/输入/预期输出逐条化 docs/e2e-test-cases.md: - 四层体系总览(双实例 pytest / M6 冒烟 65 项 / 多副本 e2e 35 项 / 压测) 与退出码约定 - 通用约定:请求信封格式、错误码契约表、Redis 真相源键、前置自检与 FLUSHDB 防误刷语义 - M6 冒烟:模板矩阵 + 13 阶段 52 条用例逐条(场景映射/输入/预期) - 多副本 e2e:S0–S8 逐条(含 DEGRADED 语义、failover 目标选择、 winner∈candidates 互斥不变量) - 双实例 12 用例与压测 3 场景的输入/判定 - 环境与重现手册(Redis DB1/DB2 约定、集群部署、逐层命令) - 已知语义差异(多副本冷突发 NO_POD_AVAILABLE、冷竞争双 Pod 自愈、 场景 N 暂缓、config_sync 串行) README/code-guide §7/CLAUDE.md 增交叉引用 Co-Authored-By: Claude <noreply@anthropic.com> fix(e2e): 经多副本 LB 跑 M6 冒烟 63/65 的根因修复——65/65 两处失败初判「多副本冷突发语义」,排查证明均为部署配置差异: 1. F-队列超时 504 缺失:集群部署漏设 AGENT_RUNTIME_SCOPE_FULL_TIMEOUT (默认 30s 恰等于 tpl-f session_ttl=30s)→ 等待者 deadline≈会话到期, 被到期驱逐的 PUBLISH 提前唤醒 → 竞态窗口内 2×NO_POD_AVAILABLE+ 2×200 混合、无干净 504。修复:部署模板补该变量(默认 8,红线注释 「须显著小于 session_ttl」)+ env.example。 2. cleanup 空目标 500:admin 凭据对不存在 ns list 得空列表,in-cluster SA 的 namespaced RBAC 先行 403 → ApiException 未处理裸 500(4/4 稳定 复现)。修复:产品 cleanup 对 404 容忍为 cleaned=0(跨凭据形态行为 对齐),403 保持 fail-fast(静默清零会掩盖 RBAC 配错);+2 单测。 测试空目标改用无匹配 label_selector——期间实测踩坑:业务 ns 会误删 同 label 真实 AgentServer(default ns 2 个 gateway 管理的 Pod 被误删, 其一 16s 自愈,handoff §十一.6 教训再现);min_idle 热备 1s 重建致 刚清空的 ns 也不为空。三坑实录入 docs/e2e-test-cases.md §8.1。 验证:M6 冒烟经 LB 65/65 + 单实例 65/65;多副本 e2e 35/35; pytest 104→106 全绿。文档计数与归因同步(CLAUDE/README/code-guide/ handoff §十一.1 补记)。 Co-Authored-By: Claude <noreply@anthropic.com> | 15 天前 |
| test(补强): 真环境缺陷复盘五项落地——真镜像门禁/自然老化/不变量巡检/停机韧性/指纹键序 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !455 merge develop into develop test(补强): 真环境缺陷复盘五项落地——真镜像门禁/自然老化/不变量巡检/停机韧性/指纹键序 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: cyz95 Description: Paired: [GitHub #104](https://github.com/openJiuwen-ai/agent-runtime/pull/104) ↔ [GitCode !455](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/455) <!-- 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**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 455 github_repo: openJiuwen-ai/agent-runtime github_pr: 104 github_branch: sync/pr-455 --> See merge request: openJiuwen/agent-runtime!455 | 7 天前 |
| docs: 文档重构支持项目记忆管理。文档三分重组——design/spec/feature 下沉模块根,spec 按子包拆分 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !439 merge develop1 into develop docs: 文档重构支持项目记忆管理。文档三分重组——design/spec/feature 下沉模块根,spec 按子包拆分 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: cyz95 Description: Paired: [GitHub #87](https://github.com/openJiuwen-ai/agent-runtime/pull/87) ↔ [GitCode !439](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/439) <!-- 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**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 439 github_repo: openJiuwen-ai/agent-runtime github_pr: 87 github_branch: sync/pr-439 --> See merge request: openJiuwen/agent-runtime!439 | 10 天前 |
| fix: 补充代码版权申明、三方引用申明、License文件 Co-authored-by: ZYQ5333<zhangyaqing8@huawei.com> # message auto-generated for no-merge-commit merge: !81 merge develop into develop fix: 补充代码版权申明、三方引用申明、License文件 Created-by: ZYQ5333 Commit-by: ZYQ5333 Merged-by: cyz95 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 task **Self-checklist**:(**请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!81 | 4 个月前 |
| fix: 补充代码版权申明、三方引用申明、License文件 Co-authored-by: ZYQ5333<zhangyaqing8@huawei.com> # message auto-generated for no-merge-commit merge: !81 merge develop into develop fix: 补充代码版权申明、三方引用申明、License文件 Created-by: ZYQ5333 Commit-by: ZYQ5333 Merged-by: cyz95 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 task **Self-checklist**:(**请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!81 | 4 个月前 |
| fix: missing studio module Co-authored-by: chen-hui-zhe-xi<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !219 merge fix-missing-studio-module into develop fix: missing studio module Created-by: chen-hui-zhe-xi Commit-by: chen-hui-zhe-xi Merged-by: cyz95 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!219 | 3 个月前 |
| fix: missing studio module Co-authored-by: chen-hui-zhe-xi<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !219 merge fix-missing-studio-module into develop fix: missing studio module Created-by: chen-hui-zhe-xi Commit-by: chen-hui-zhe-xi Merged-by: cyz95 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!219 | 3 个月前 |