Ironclad / Ironclad/rivet

[Bug]: Rivet screen blanks out; Uncaught RangeError: Maximum call stack size exceeded

Open
#411 3 comments 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?

While using a project with 16 subgraphs for awhile during a single session, I've occasionally had the Rivet application screen go completely blank (gray) when right-clicking on the Graphs area to create a new Subgraph. After this, I cannot save the project or do anything with the UI.

In the F12 console, I found "Uncaught RangeError: Maximum call stack size exceeded".

### What was the expected functionality?

UI should not go blank.

### Describe your environment

Windows 11
Node v20.11.1
Rivet 1.7.12

### Relevant log output

See attachment in next comment.

### 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

Reproduce the issue in the Rivet UI by using a project with 16 subgraphs, waiting during a session, and right-clicking the Graphs area to create a new Subgraph. Start with the F12 console and the reported RangeError; done means the screen stays usable and the project can still be saved.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.