Cache workflow event prefixes and immutable refs#2256
Draft
pranaygp wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
Contributor
🦋 Changeset detectedLatest commit: cd6a045 The changes in this PR will be included in the next version bump. This PR includes changesets to release 17 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
world-vercel, with LRU eviction and in-flight request coalescingDesign
The event-log cache lives in the runtime so it applies to any
Worldimplementation used for replay. Entries are scoped byWorldinstance to prevent mixing run/cursor state across backing stores or tenants, and every replay still fetches the append-only tail after the cached cursor.Remote ref caching stays in
world-vercel: remote ref descriptors and the ref endpoint are adapter transport details, not part of the genericWorldcontract. The adapter retains only bounded immutable bytes and decodes fresh values for callers.Memory Bounds
Validation
pnpm --filter '@workflow/core...' buildpnpm --dir packages/core test(1,092 tests passed)pnpm --dir packages/world-vercel exec vitest run src(116 tests passed)git diff --check origin/main...HEADpnpm changeset status --since=main