-
-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ferrum::BrowserError: Message may have string 'sessionId' property #477
Comments
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'd need a full debug log or a minimal reproducible case. |
What do I need to do to get a full debug log, what does it need to include? |
I've managed to get a debug log:
I'll see if I can extract a minimal reproducible case from my code tonight |
I don't see where you created 3 Target in the log, how do you create pages? Can you show simplified test at least? |
So this is running as an Rspec test using Cuprite and Capybara. At present I only have a test as setup within our app running rails. The test is simply a visit, which is where it falls over:
I dont believe we are doing anything special regarding our Cuprite setup:
This is the log for that test above:
Could this be a bug in Cuprite instead, should I raise an issue there instead. |
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 contains the IP address of the docker container running our Chrome instance |
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? |
This is running a docker setup locally. The same setup works correctly with ferrum 0.14 and cuprite 0.15. However upgrading to ferrum 0.15 and cuprite 0.15.1 it starts to fail. The only changes are these 2 gems. The same docker setup works with the previous versions. |
Describe the bug
When upgrading to Ferrum 0.15 using Cuprite 0.15.1 we get errors in all our tests. The error being returned is
Ferrum::BrowserError: Message may have string 'sessionId' property
. This seems to be an error returned from Chrome itself. Looking at the messages being sent I can see that sessionId is being passed to the message with a value of nil. I've compared this to messages being sent by 0.14 where it worked and can see there that sessionId is excluded.To Reproduce
I've managed to get a los of all messages that have been send to chrome from the Client.
Expected behavior
Expect messages to be sent without issue to Chrome. As in 0.14.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: