Skip to content

fix(server): share JJ caches between workflow and review - #1

Open
omarshaarawi wants to merge 2 commits into
gergesh:yoav/jj-supportfrom
omarshaarawi:jj-share-driver-cache
Open

omarshaarawi wants to merge 2 commits into
gergesh:yoav/jj-supportfrom
omarshaarawi:jj-share-driver-cache

Conversation

@omarshaarawi

Copy link
Copy Markdown

The JJ workflow and VCS registry construct separate drivers, so workflow cache invalidation leaves review metadata stale. After a remote rename, a warmed registry-backed review can return an empty diff even though the workflow driver resolves the new remote correctly.

The registry now consumes the existing JJ service. Both paths use the same exported Effect layer and share its caches. The regression uses a real JJ repository to warm a review diff, rename its remote, invalidate caches through the service, and verify the registered driver still reports the changed file and correct base.

Verified with JJ 0.44.0. The regression failed before the fix and passes after it. All eight tests in VcsDriverRegistry.test.ts, the server typecheck, and lint and formatting checks for the two changed files pass.

Implemented with GPT-6 Astra. Reviewed and integrated with GPT-6.1 Sol and GPT-6 Sol through the Codex harness in T3 Code.

@github-actions github-actions Bot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:XS labels Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS vouch:unvouched PR author is not yet trusted in the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant