Ironclad / Ironclad/rivet

[Bug]: Rivet editor shows wrong data flow

Open
#480 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### What happened?

In a case where:
- Executor is "Node"
- An array is fed into a subgraph
- The subgraph is in "Split - Sequential" mode
- The subgraph has a code node with compute-intensive code

the editor shows wrong dataflow in a subgraph when switching between runs (1, 2).

You can see wrong data flow after the "MATCH" node:

![Image](https://github.com/user-attachments/assets/4096e042-93b9-4eff-a8e0-b1a0e6d5b16d)
![Image](https://github.com/user-attachments/assets/bfc6592c-bd5f-4142-93c4-2e3829258207)
![Image](https://github.com/user-attachments/assets/c27a19b2-7fbe-4c9f-872c-ef3e2b98e26b)

### What was the expected functionality?

The editor shows correct dataflow in a subgraph when switching between runs (1, 2).

### Describe your environment

Windows, Rivet 1.10.1

### Relevant log output

```shell

```

### Relevant screenshots

_No response_

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the Rivet editor with the Node executor, an array-fed subgraph in Split - Sequential mode, and a compute-intensive code node. Switch between runs 1 and 2 and inspect the dataflow after the MATCH node; done means the subgraph displays the correct dataflow for both runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.