Hmmm, a site that I use etaoin to scrape pages on has changed their stuff so that get-source now always times out even though I can physically interact with the page just fine. Some known trick here?
SocketTimeoutException Read timed out java.net.SocketInputStream.socketRead0 (SocketInputStream.java:-2)
Every time.
I'm pretty hosed without get-source. get-window-handles works though.
Hmmm, that was etaoin 0.1.8 snapshot. 0.2.8 snapshot won't run the chrome driver I have. Just gonna be one of those days I guess.
To be clear, it was something in the host site that changed and broke get-source. Is there some websocket or session security or other thing they might have adopted that would break get-source ?
Well, on not finding the driver, I see the :path option to boot-driver is now :path-driver, so a breaking change.
On the socket read timeout, I've figured that out too, I was calling get-source on a window that had been closed (the host now has a dual window scheme). All set for now.
Calling switch-window to a viable window solves the problem.