-
Notifications
You must be signed in to change notification settings - Fork 11k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IF ELSE can cause the Stream output of LLM nodes to fail. #12068
Comments
The issue you're experiencing with the stream output failure in LLM nodes when using a variable aggregator might be related to the requirement that the variable aggregator can only aggregate variables of the same data type. If the first variable added to the aggregator is of a certain type, all subsequent variables must match this type. This restriction could lead to issues if there is a mismatch in data types among the variables being aggregated [1]. To troubleshoot this, ensure that all variables being aggregated are of the same data type. If the problem persists, check for any specific error messages or logs that might provide more insight into the failure. Additionally, verify that the variable aggregator is correctly configured to handle the data types involved in your workflow. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
After I removed the variable aggregator, the output is still blocking rather than streaming. Could you please guide me on how to modify the yml file to resolve this issue? |
can you share your dsl? |
in |
Oh, it seems the issue is not caused by the variable aggregator, but rather by the IF ELSE statement. |
do we have the same dsl it seems different |
Include branch node stream output not working #9852 |
The DSL I tested for another person also has the issue that the LLM stream output fails after the IF node. |
Signed-off-by: yihong0618 <[email protected]>
Signed-off-by: yihong0618 <[email protected]>
This bug was marked as fixed. However, I just ran into a similar issue when I added an If-Else node before the LLM node. |
Yes, 0.14.2 does not have this fix yet. |
can you help about that? I think there still other case about this. |
I also encountered a similar issue . my dsl
|
The problem of categorizing branches of the problem still exists. |
It's not just conditional branching, it's also a problem with problem classifiers. |
You misunderstood me. I meant that the latest 0.14.2 does not include this fix yet, it will be in the next version. |
If you want to check if #12105 has fixed your issue, please start the test from the source code. |
Thanks |
Self Checks
Dify version
0.14.2
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
MyDSL
✔️ Expected Behavior
Stream output
❌ Actual Behavior
Stream failed
The text was updated successfully, but these errors were encountered: