Ironclad / Ironclad/rivet

[Bug]: "Append To Dataset" node lacks error for dataset not found

Open
#325 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?

"Append To Dataset" node keeps running forever, even though it failed (see screenshot)
This only happens with the node-executor!

### What was the expected functionality?

"Append To Dataset" node should have returned error: "Dataset core_memory not found"

### Describe your environment

MacOS, Node 14.0.0, etc.

### Relevant log output

_No response_

### Relevant screenshots

![image](https://github.com/Ironclad/rivet/assets/149181237/e00dc355-9295-426d-9d76-4f7a3274ac53)

### Code of Conduct

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

Contributor guide

Open the contributing guide

Research direction

Locate the “Append To Dataset” node and its node-executor path, then reproduce the case where dataset core_memory is missing. Confirm that execution terminates with the expected “Dataset core_memory not found” error instead of running indefinitely.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.