Kevin9703
Kevin9703
同问，你解决了吗
4.1.14 同样遇到了这个问题，只有第一次点击有响应
我单独一个子应(umi4)用用webpack5 也会报错 Error: Container initialization failed as it has already been initialized with a different share scope
同问，debug看是返回的页面内容没了，你解决了吗
In this PR https://github.com/langgenius/dify/pull/12037, the logic for identifying the o1 model has been changed from "o1" in model to model.startswith("o1"), which causes incorrect model identification and leads to calling errors....
I agree that we should upgrade the Weaviate version. Version 1.2x supports different compression methods and gRPC calls, which can significantly improve performance.
> I encountered the same problem, simple workflows are normal, but complex workflows do not have streaming outputs. version:0.14.2 +1 Experiencing exactly the same issue
@laipz8200 Sorry to bother you. At your convenience, could you please review this issue? It's currently impacting our production business. Really appreciate your help.
> > @laipz8200 Sorry to bother you. At your convenience, could you please review this issue? It's currently impacting our production business. Really appreciate your help. > > can you...
> can you try this patch @Kevin9703 @ritamariavermelho06 #12355 Works now! But wondering what was the root cause? ?