fix(cli): avoid bridge detectElements timeout#89
Merged
steipete merged 2 commits intosteipete:mainfrom Mar 13, 2026
Merged
Conversation
steipete
force-pushed
the
upstream-fix-bridge-capture-reliability
branch
from
15079ed to
5d79d42
Compare
Owner
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
2 participants
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 #81
Uses the command timeout for remote
detectElementsrequests instead of the bridge client's default 10 second socket timeout. On slower bridge captures the detection work can finish just after 10 seconds, which currently turns a successful scan into anOperation timed outerror inpeekaboo see.The CLI still keeps its wall-clock timeout, but remote detection requests now get a small cushion above that limit.