Ironclad / Ironclad/rivet

[Feature]: "run from here"

Open
#343 2 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### Feature Request

When adding to a bigger graph, appending/iterating on new functionality can mean waiting a good while to test a minor change.

I know there's caching, but if you have RNGs in your path, caching doesn't work.

P.S. _Love_ the tool and the work on it. I've almost completely replaced key notebooks with Rivet.

### Code of Conduct

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

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing graph execution and caching behavior in the Rivet codebase, focusing on how a larger graph is run and how RNGs affect caching. Define what selecting “run from here” should execute and how completion can be verified for graphs containing non-cacheable RNG steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.