PAB-56: cache dashboard runtime URL config - #72
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Kody Review CompleteGreat news! 🎉 Keep up the excellent work! 🚀 Kody Guide: Usage and ConfigurationInteracting with Kody
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
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.
This pull request streamlines the runtime URL config by replacing the ad‑hoc cache in
src/server/tailscale/urls.tswith the shared in‑memory cache (getOrSet/invalidate). The new implementation deduplicates parallel calls so that multiple concurrent dashboard requests (e.g., when building project URLs) perform only onegetTailscaleConfiglookup. The invalidation path used after connect/disconnect operations is also updated to use the shared cache key.Additionally, the monitor page (
src/pages/monitor.astro) was fixed to scope the project query to the currently authenticated user – previously it returned all non‑deleted projects regardless of ownership, which is now restricted toownerUserIdmatching the session user.