[Bug]: Serious issues with subgraph splitting + running graphs via rivet-node
- Dominant language
- TypeScript
- Stars
- 4.7k
- Forks
- 388
- PR merge metrics
- No merged PRs in 30d
Description
### What happened?
I have a subgraph that is succesfully running, but the output of the subgraph returns that it has 4x not run instead.
Looks like if the 1st iteration is "Not ran" that all other iterations will also be "Not ran" even if that is not the case:
This issue does not happen if the 1st iteration returns something and later iterations do not return something.
### What was the expected functionality?
I like to be able to use splitting + subgraph to filter data.
### Describe your environment
MacOS, Node 14.0.0, etc.
### Relevant log output
_No response_
### Relevant screenshots
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by reproducing the reported case with a split subgraph run through rivet-node on the stated Node 14 environment. Compare iteration results when the first iteration is not run with cases where it returns a value; done when later iterations retain their actual results and can be used to filter data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- ai, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100