Repository navigation
fix(mobile): unwrap batched observer telemetry #5805
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
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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.
[P1] Publish once after storing the whole relay envelope
_storeFramestill calls_emitfor every inner frame, so unwrapping a batch of N produces N full state publications. Each publication snapshots every retained agent list (_snapshotFrames), and every channel-scoped provider watching this state filters the list and rebuilds its transcript (observer_subscription.dart:350-365);app.dart:87also keeps the relay provider live app-wide. A normal publisher batch can therefore turn one relay event into repeated sorting, copying, transcript derivation, and UI rebuilds, with quadratic-looking work as the batch grows. This is precisely the backpressure batching is meant to preserve; desktop commits the full envelope and explicitly tests one external-store notification per batch (observerRelayStore.ts,activeAgentTurnsStore.test.mjs). Make_storeFramemutate/return whether it changed state, then clear the error and call_emitonce after the loop. Add a provider-observer regression asserting one state update for a multi-frame batch.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.
🤖 Addressed in 9154fc3 by publishing at most one successful observer state update per relay envelope, only when storage changes. Added a provider-listener regression that pins one update for a multi-frame batch and none for an all-duplicate replay.