Repository navigation
fix(client-runtime): branch picker shows branches changed outside T3 Code #27438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
maria-rcks
merged 5 commits into
pingdotgg:main
from
ebrahimHakimuddin:fix/branch-picker-refresh-refs
Nov 3, 2026
+107
−2
Merged
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
f2e2ce4
fix(client-runtime): branch picker shows branches changed outside T3 …
ebrahimHakimuddin eb331a9
Merge branch 'main' into fix/branch-picker-refresh-refs
ebrahimHakimuddin b3d3eab
Merge remote-tracking branch 'github/main' into takeover-27438
maria-rcks f619a97
fix(client-runtime): share ref refresh freshness across list keys
maria-rcks 51195d5
Merge branch 'main' into fix/branch-picker-refresh-refs
ebrahimHakimuddin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script executed:
Repository: pingdotgg/t3code
Length of output: 6042
Script executed:
Repository: pingdotgg/t3code
Length of output: 16398
Refresh the first request after the relevant invalidation without using a permanent positive-revision check.
The stale-request finding remains valid. A new list key starts with
builtRevision === undefined, so its first request can omitrefresh: trueafter the picker invalidates refs.Do not fix this with
state.revision > 0. The environment revision is kept alive and only increases. That condition would make the first request for every later-created or rebuilt key bypass the snapshot for the lifetime of the environment. It would not bypass every request from one key, but it could cause repeated unnecessary ref scans as query keys change. This conflicts with the stated first-load snapshot behavior.Use a one-shot freshness marker scoped to the relevant invalidation and list key, and add a test for a key first built after invalidation. The available evidence does not establish a safe localized implementation for that marker, so no code diff is proposed.