Skip to content

feat(observability): fix model name - #62

Open
openjiuwen-sync-bot[bot] wants to merge 2 commits into
openJiuwen-ai:730from
openjiuwenai:sync/pr-202
Open

feat(observability): fix model name#62
openjiuwen-sync-bot[bot] wants to merge 2 commits into
openJiuwen-ai:730from
openjiuwenai:sync/pr-202

Conversation

@openjiuwen-sync-bot

@openjiuwen-sync-bot openjiuwen-sync-bot Bot commented Jul 31, 2026

Copy link
Copy Markdown

Paired: GitHub #62GitCode !202

What type of PR is this?

/kind

Self-checklist:(请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入

    • 设计:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改
    • 测试:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库
    • 验证:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述
    • 接口:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确
    • 文档:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

- OlteRail: fix model name
@openjiuwen-collaboration-bot

Copy link
Copy Markdown

head_sha: 6a4a70b02579974791b8afc4e50ea3e1dcdc5204

TASK STATUS DETAILS
CodeCheck ✅SUCCESS Click here
AntiPoison ✅SUCCESS Click here
Software Composition Analysis ✅SUCCESS Click here
Maven Build ✅SUCCESS See CHECK tab

@openjiuwen-collaboration-bot

Copy link
Copy Markdown

head_sha: 6a4a70b02579974791b8afc4e50ea3e1dcdc5204

TASK STATUS DETAILS
CodeCheck ✅SUCCESS Click here
AntiPoison ✅SUCCESS Click here
Software Composition Analysis ✅SUCCESS Click here
Maven Build ❌FAILED See CHECK tab

## 主要变更

### 分层团队工具ID冲突修复
- HierarchicalDelegateTool/DelegateTool 的 toolId 添加 "_delegate_tool" 后缀,
  避免与同名 agent 在 ResourceMgr tagMgr 中注册冲突
- 工具名称(toolName)保持不变,对 LLM 仍暴露子 agent ID

### 分层团队工具注入逻辑优化
- HierarchicalToolsTeam/HierarchicalMsgBusTeam 移除注入前的存在性检查
- 改用 addTool(tool, parentId, refresh=true) 强制刷新,
  防止旧工具实例残留导致 "Tool instance not found" 错误

### ResourceMgr 健壮性增强
- 批量注册(agent/workflow/tool)增加类型校验,非法类型抛出明确错误
- getTool 对空 ID 抛出 RESOURCE_ID_VALUE_INVALID 异常
- getResourceByTag 跳过 null 条目而非加入结果列表
- innerAddResource 重复注册时返回 Error 而非静默替换
- 新增 pythonTypeName 辅助方法,错误信息对齐 Python SDK

### TagMgr 空值处理对齐 Python
- getResourcesTags 返回空列表替代 null
- removeResourceTags 在 skipIfNotExists=false 时校验不存在的标签
- doRemoveResourceTags/doRemoveTag 清理空 tag 和空 resource 映射

### ToolCard 模型类支持
- 新增 inputParamsRaw 字段及重载 builder 方法,
  支持 Pydantic 模型类作为工具输入参数(对齐 Python input_params 类型)

### TaskManager 级联取消
- 实现子任务级联取消逻辑

## 测试验证
- 4个分层团队冒烟测试全部通过
- 完整 smoke 套件 323 个测试 0 失败 0 错误
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants