Frozen state: start cold rebuilds and inspection from the latest whole copy

Open
#5,324 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Read the implementation of recoverStateContext, createRunStateHydrator, and workflow inspect, along with the events API and the whole-copy format described in #5215. First trace how each reader currently pages and applies events; then investigate descending pagination, skip-step-inputs, multi-log inputs, and StateSrcV1 hook payloads. Done means the three readers can start from the latest usable whole copy while replay still reads the full log.

Written by the indexing model from the issue text.

Description

Follow-up from #5215.

Frozen state is now written whole each time it doubles, and after every 1,000 changes, so a rebuild never has to apply more than about the value's own size of changes. But every reader still reads the run's log from the start:

  • cold recovery (recoverStateContext) pages through every event from the beginning;
  • the o11y hydrator (createRunStateHydrator) and workflow inspect do the same.

So the whole copies bound the apply work, not the read. On a 180-turn eve session, a cold rebuild at turn 180 took 228 ms: 60 ms parsing and 168 ms applying, both proportional to the whole log.

Proposal: have these readers read the log newest-first until they reach the latest whole copy of each version they need, then apply forward from there. A cold read is then bounded by about twice the value's size rather than the length of the run. Replay is unaffected: it reads the full log anyway.

Open questions:

  • the events API needs to support descending pages with skip-step-inputs;
  • a step input can refer to more than one log, so the reader has to keep going until every needed log has reached a whole copy;
  • hook payloads that hold strings a patch refers to (StateSrcV1) may come before that whole copy.

🤖 Generated with Claude Code

Dominant language
TypeScript
Stars
2.5k
Forks
401
Avg merge
1d 21h
Merged PRs (30d)
201

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/workflow

All issues in vercel/workflow

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.