fix(state): wire up wait_for_stable_ui dead config field - #420
Open
lesurJ wants to merge 1 commit into
Open
Conversation
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.
wait_for_stable_uiwas read intoAgentConfigbut never consumed anywhere in the codebase, so a well-formed-but-stale accessibility dump (e.g. a WebView a11y bridge lagging behind a client-side route change) was accepted immediately with no retry; this wires the setting intofetch_state_with_retry/AndroidStateProvider, adding a bounded re-poll loop that waitswait_for_stable_uiseconds and compares consecutivea11y_treedumps, returning as soon as two agree (or giving up after_MAX_STABILITY_CHECKSrounds), withdroid_agent.pynow passing the configured value through instead of it silently doing nothing.