Ironclad / Ironclad/rivet

[Bug]: Node.js executor always crashes if using image + google (chat)

Open
#312 3 comments 1 reaction 1 assignee Claimed by @gogwilt View on GitHub
bug
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### What happened?

Node.js executor always crashes if using image + google (chat); see screenshot attached.
As a user that means that you cannot even abort the run of the graph (button missing).

### What was the expected functionality?

- Node.js executor does not crash
- "Abort" button will still be available even if node.js executor crashes
- After you aborted the graph Rivet will automatically start a new node.js executor so you don't have to restart the program

### Describe your environment

MacOS, Node 14.0.0, etc.

### Relevant log output

_No response_

### Relevant screenshots

![image](https://github.com/Ironclad/rivet/assets/149181237/1481cd5b-cc21-4e3b-b9f5-51509eb9f9b5)

### Code of Conduct

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.