fix(agents): pin GitHub reads to HEAD so new agents appear - #524
Merged
Conversation
Co-authored-by: Ry <4283+ryw@users.noreply.github.com>
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
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.
Fixes #493.
New agents committed outside TAS (Tembo CAP, a direct push, YOLO mode) could 404 and stay missing from the Agents list and search for minutes. GitHub Contents reads were cached for 60s against the branch name, including 404s, and nothing busted that cache on an external commit.
Contents reads now pin to the current HEAD sha (5s in-process debounce, coalesced per replica). A new commit is a new cache key, so the next page load sees the file within a few seconds instead of serving a stale listing or cached 404.
TAS writes still call
updateTagand pin HEAD to the write’s commit sha for read-your-own-writes.