Dmitry Vorotilin
Dmitry Vorotilin
It's not cuprite/ferrum issue, find the version that still works
Interesting, @noniq could you try to activate given page with https://github.com/rubycdp/ferrum/commit/600d63d0a2b1fd7787f69038ffeb9eabcc6c2f49 for ferrum 0.15
hm I think wrong target is active, I have a sense what's going on. Let me try to reproduce it with pure Cuprite test
Send a PR :)
New Ferrum has a new feature included, flatten mode, so we use one socket connection to all pages, versus having socket per page. To understand why there's no session id...
I don't see where you created 3 Target in the log, how do you create pages? Can you show simplified test at least?
Let's keep the convo here for now, I'll take care of it. I first need to understand where the issue lies
What is `chrome_ip`? The only outlier I noticed
This is the issue I'd say. What is your setup? The docker is running locally or we talk about CI? Does it work locally?
@ibrahima I'm on vacation currently and will take a look on Monday or sooner if I have time