I tried this:
Calling buildGraph on workflows from the use cases defined in the specification repo. Both the managing-github-issues and multi-agent-ai-content-generation examples crash.
This happened:
buildGraph crashes with
RangeError: Maximum call stack size exceeded
at Array.findIndex (<anonymous>)
at graph-builder.ts:282
at Array.filter (<anonymous>)
at buildTransitions (graph-builder.ts:280)
at buildGenericTaskNode (graph-builder.ts:325)
at buildCallTaskNode (graph-builder.ts:336)
at buildTaskNode (graph-builder.ts:297)
at buildTransition (graph-builder.ts:252)
Both workflows use then directives that loop back to a previous step. For example, in the ai-content workflow, the refine step has then: evaluateQuality, and in the github-issues workflow, awaitDetailsFromQA has then: awaitForDevWork. The cyclical then references seem to be the issue.
I expected this:
buildGraph should successfully return a graph for all use cases
Is there a workaround?
Not that i'm aware, it will require a bug fix
Anything else?
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞
I tried this:
Calling
buildGraphon workflows from the use cases defined in the specification repo. Both themanaging-github-issuesandmulti-agent-ai-content-generationexamples crash.This happened:
buildGraph crashes with
Both workflows use
thendirectives that loop back to a previous step. For example, in the ai-content workflow, therefinestep hasthen: evaluateQuality, and in the github-issues workflow,awaitDetailsFromQAhasthen: awaitForDevWork. The cyclicalthenreferences seem to be the issue.I expected this:
buildGraphshould successfully return a graph for all use casesIs there a workaround?
Not that i'm aware, it will require a bug fix
Anything else?
No response
Community Notes