fix(usage): batch live session refresh - #58
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
get_session_usageRPC per running session with oneget_sessions_usagebatch per bridgeftown-bridgeto 0.19.7Root cause
The UI mapped a per-session RPC across every running session. Both each running-ID-set change and a 15-second interval invoked that unbounded fan-out. One prior E2E bridge run recorded 217 usage commands in roughly three and a half minutes.
Result
For N eligible sessions on one bridge, a normal refresh now emits one bridge command instead of N. Shell, Cursor, completed sessions, sessions without a native transcript ID, and hidden tabs emit no periodic usage requests.
Validation
ftown-bridge-0.19.7.tgz