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

ai-made-approachable commented 8 months ago

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

Code of Conduct

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

codemile commented 8 months ago

I'll take a look at this in a bit. I need to setup a Google account, etc. to work on it.

gogwilt commented 8 months ago

@ai-made-approachable can you upload the image you used to test this with? I cannot reproduce this on Rivet 1.7.5, and I wonder if the issue is perhaps that you used a very large image.

ai-made-approachable commented 8 months ago

@gogwilt : I can also not reproduce it on 1.7.5 anymore. Now everything executes much quicker and then only google fails with a response: "Error: Error processing ChatGoogleNode: Error processing stream because response === undefined"

Ironclad / rivet