ModelEngine-Group / ModelEngine-Group/app-platform

工具流调用出错

Open
#246 1 comment 0 reactions 1 assignee View on GitHub

@XinLi-cyber is already working on this.

Since Jun 12, 2025.

in: builder status: waiting-for-triage type: bug
Dominant language
Java
Stars
1.5k
Forks
233
PR merge metrics
No merged PRs in 30d

Description

问题摘要 / Issue Summary

创建的工具流执行失败

版本信息 / Version Information

v1.0.1 (最新版 / Latest)

浏览器 / Browser

No response

操作系统 / Operating System

None

发生了什么?/ What happened?

创建一个工具流并发布,在流程编排中拖拽工具流或者在并行节点中添加工具流,执行出错。

期望的行为 / Expected Behavior

期望执行工具流成功

重现步骤 / Steps to Reproduce

1、创建一个工具流并发布
2、创建一个应用,选择并行节点或循环节点,添加发布的工具流,或者直接将工具流添加到流程中
3、调试会在添加工具流的地方报错。

相关日志 / Relevant Logs
Caused by: java.lang.IllegalArgumentException: Name cannot be blank.


at modelengine.fitframework.inspection.Validation.notBlank(Validation.java:538)


at modelengine.fitframework.parameterization.support.DefaultResolvedParameter.<init>(DefaultResolvedParameter.java:35)


at modelengine.fitframework.parameterization.support.DefaultParameterizedString$Resolver.resolveSuffix(DefaultParameterizedString.java:322)


at modelengine.fitframework.parameterization.support.DefaultParameterizedString$Resolver.resolve(DefaultParameterizedString.java:203)


at modelengine.fitframework.parameterization.support.DefaultParameterizedString.resolve(DefaultParameterizedString.java:154)


at modelengine.fitframework.parameterization.support.DefaultParameterizedStringResolver.resolve(DefaultParameterizedStringResolver.java:85)


at modelengine.fitframework.util.StringUtils.format(StringUtils.java:288)


at modelengine.fitframework.util.StringUtils.format(StringUtils.java:266)


at modelengine.fitframework.util.StringUtils.format(StringUtils.java:251)


at modelengine.fit.jober.aipp.service.impl.AippRunTimeServiceImpl.lambda$createAippInstance$0(AippRunTimeServiceImpl.java:143)


at java.base/java.util.Optional.orElseThrow(Optional.java:403)


at modelengine.fit.jober.aipp.service.impl.AippRunTimeServiceImpl.createAippInstance(AippRunTimeServiceImpl.java:142)


at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)


at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)


at java.base/java.lang.reflect.Method.invoke(Method.java:569)


at modelengine.fitframework.util.ReflectionUtils.invoke(ReflectionUtils.java:540)


at modelengine.fitframework.aop.proxy.support.JdkDynamicProxy.lambda$invoke$0(JdkDynamicProxy.java:43)


at modelengine.fitframework.aop.proxy.support.AbstractAopProxy.invoke(AbstractAopProxy.java:86)


at modelengine.fitframework.aop.proxy.support.JdkDynamicProxy.invoke(JdkDynamicProxy.java:38)


at modelengine.fit.jober.aipp.service.impl.AippRunTimeServiceImpl$$Fit$ByteBuddy$$3brvYsyY.createAippInstance(Unknown Source)


at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)


at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)


at java.base/java.lang.reflect.Method.invoke(Method.java:569)


at modelengine.fitframework.util.ReflectionUtils.invoke(ReflectionUtils.java:540)


at modelengine.fitframework.broker.support.LocalFitableExecutor.execute(LocalFitableExecutor.java:111)
额外信息 / Additional Context

No response

确认事项 / Confirmations
  • 我已经搜索了现有的issues,确认这不是重复问题
    I have searched existing issues and confirmed this is not a duplicate

  • 我已经阅读了项目文档和 FAQ
    I have read the project documentation and FAQ

  • 我提供的信息准确完整
    The information I provided is accurate and complete

  • 我愿意协助测试问题修复 (可选)
    I'm willing to help test the bug fix (optional)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.