类型不匹配?
#510
Replies: 1 comment
-
|
That's correct. We found that WhileLoopPipeline often created workflows that were difficult for developers to debug and control. For this reason, we have deprecated it in the latest version. The recommended approach is now to construct the workflow explicitly, which provides greater clarity and makes the logic easier to follow. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Workstation中的Group Chat示例,导出的代码:
flow = Noneflow = Msg(content="Hello every one", name="User", role="user")…………
pipeline_5 = WhileLoopPipeline(loop_body_operators=[pipeline_6], condition_func=lambda *args: True)…………
flow = pipeline_5(flow)pipeline.py 中:
class WhileLoopPipeline(PipelineBase):…………
def __call__(self, x: Optional[dict] = None) -> dict:return whilelooppipeline(loop_body_operators=self.loop_body_operators,condition_func=self.condition_func,x=x,)看这里这个__call__的定义中接收的参数类型,为什么pipeline_5能接受flow(Msg对象)啊。
Beta Was this translation helpful? Give feedback.
All reactions