etaoin

jdt 2018-06-12T11:43:27.000240Z

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?

jdt 2018-06-12T11:44:16.000244Z

SocketTimeoutException Read timed out java.net.SocketInputStream.socketRead0 (SocketInputStream.java:-2)

jdt 2018-06-12T11:44:18.000339Z

Every time.

jdt 2018-06-12T11:56:01.000365Z

I'm pretty hosed without get-source. get-window-handles works though.

jdt 2018-06-12T12:04:05.000117Z

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.

jdt 2018-06-12T12:34:08.000022Z

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 ?

jdt 2018-06-12T22:49:03.000384Z

Well, on not finding the driver, I see the :path option to boot-driver is now :path-driver, so a breaking change.

jdt 2018-06-12T22:52:59.000179Z

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.

jdt 2018-06-12T22:53:25.000350Z

Calling switch-window to a viable window solves the problem.