fix(deepresearch): fix ResearchTeamNode error and missing edge from research_team to planner, preventing possible infinite loop #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
本PR修复以下问题:
ResearchTeamNode目前的逻辑会造成进入parallel_executor后可能出现curPlan为null的现象,且可能因此造成research_team_next_node一直为parallel_executor而造成流程进入research_team后死循环。ResearchTeamDispatcher,默认的情况下路径会进到planner,而DeepResearchConfiguration中从research_team出发的conditionalEdge缺少planner的mapping,因此也会造成流程无法运行到END。This PR addresses and fixes the following issues:
ResearchTeamNode's current logic can lead to a scenario wherecurPlanbecomesnullafter entering theparallel_executor. This can subsequently cause theresearch_team_next_nodeto perpetually remain theparallel_executor, resulting in a deadlock once the flow enters theresearch_team.ResearchTeamDispatcher, the default path leads to theplanner. However, theDeepResearchConfigurationis missing theplannermapping in the conditional edge starting from theresearch_team, which also prevents the flow from reachingEND.