bug-点击控件引起WDA超时,概率较高
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 469
- PR merge metrics
- No merged PRs in 30d
Description
File "F:\GitLab\apprunner\venv\lib\site-packages\selenium\webdriver\remote\webelement.py", line 80, in click
self._execute(Command.CLICK_ELEMENT)
File "F:\GitLab\apprunner\venv\lib\site-packages\selenium\webdriver\remote\webelement.py", line 633, in _execute
return self._parent.execute(command, params)
File "F:\GitLab\apprunner\venv\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute
self.error_handler.check_response(response)
File "F:\GitLab\apprunner\venv\lib\site-packages\appium\webdriver\errorhandler.py", line 31, in check_response
raise wde
File "F:\GitLab\apprunner\venv\lib\site-packages\appium\webdriver\errorhandler.py", line 26, in check_response
super().check_response(response)
File "F:\GitLab\apprunner\venv\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 242, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Could not proxy. Proxy error: Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded
@codeskyblue
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported click path in selenium/webdriver/remote/webelement.py and the Appium error handling in appium/webdriver/errorhandler.py. Reproduce the click against WDA and trace the proxy timeout; done means the recurring 240000ms timeout is explained and the click completes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, python
- Domain
- mobile-dev, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100