al3xkras
commented
1 month ago Hi Mark,
Normally, when the error occurs at "line 368, in play await wait_until(driver, C.wait_2s, find_element_and_click(...)", the bot should reload the page if game controls are visible and --next-game-auto is set to True. Otherwise the bot will raise TimeoutException and start a new game (or more specifically, treat an existing game as if it was a new game).
To solve this error I ended up reloading the page entirely, as more optimal solutions didn't seem to work. I think, that it might have been related to the selenium backend, which is sometimes unable to locate dynamically added elements.
I have implemented a possible solution on the test branch, by changing the logic of when the page should be reloaded. This should help avoiding situations, where Selenium does not recognise the first dynamically added element.
To check if it works for you, clone the test branch:
git clone -b test --depth 1 https://github.com/al3xkras/chess-com-bot-selenium chess-com-bot-test
If the last commit did not solve the issue, I might additionally require the following information:
-
Is the command line argument --next-game-auto set to False?
-
Have you changed any default settings on the chess.com page?
-
How often does the error occur? (always/from time to time)
-
Which time control was set when the error occurred? (1 min / 5 min / 10 min / ...)
Kind regards, Alexander
mark-baumann
Hey Alex,
i installed your script on my Windows Machine. The first move works without problem, but then I will get this error Message:
(main.py:573)←[0m ←[0m2024-07-17 11:37:52 ←[32m[INFO] [←[32mchess-log,←[32m main.py:407]←[0m←[38;20m: Board: <selenium.webdriver.remote.webelement.WebElement (session="dc029f43251280d13b91a861176a20cc", element="f.0EC23E972DB1C283AADEEC4C3844C71E.d.EDFE93657D922298F600B4983D78FD9C.e.128")>←[0m ←[0m2024-07-17 11:37:52 ←[32m[INFO] [←[32mchess-log,←[32m main.py:419]←[0m←[38;20m: Is playing black pieces: False←[0m ←[0m2024-07-17 11:37:52 ←[33;20m[DEBUG]←[36m [chess-log,←[36m main.py:215]:←[0m←[38;20m <play> call took 0.000000s←[0m ←[31;20m 2024-07-17 11:37:54 [chess-log]: Traceback (most recent call last): File "C:\Users\mark\Desktop\chess-com-bot\main.py", line 565, in loop return await actions(engine, driver) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\mark\Desktop\chess-com-bot\main.py", line 457, in actions await play(driver_, engine, mv_) File "C:\Users\mark\Desktop\chess-com-bot\main.py", line 380, in play raise e File "C:\Users\mark\Desktop\chess-com-bot\main.py", line 368, in play await wait_until(driver, C.wait_2s, find_element_and_click( File "C:\Users\mark\Desktop\chess-com-bot\main.py", line 238, in wait_until return await CustomTask( ^^^^^^^^^^^^^^^^^ File "C:\Users\mark\Desktop\chess-com-bot\main.py", line 236, in wait_until_sub return WebDriverWait(drv_, delay_).until(condition_) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\mark\Desktop\chess-com-bot\venv\Lib\site-packages\selenium\webdriver\support\wait.py", line 105, in until raise TimeoutException(message, screen, stacktrace) selenium.common.exceptions.TimeoutException: Message:How can I solve this?
Kind regards Mark