Chromedriver Devtools port number error - ruby

I'm getting the following error while trying to run tests using capybara, selenium and chromedriver-helper. The tests run fine locally on a mac using the same version of chromedriver. I've tried setting the remote debugging port explicitly in my spec_helper, but apparently this is ignored as chromedriver uses a random remote debugging port.
Selenium::WebDriver::Error::UnknownError:
unknown error: Devtools port number file contents <37329> were in an unexpected format
(Driver info: chromedriver=2.40.565383 (76257d1ab79276b2d53ee976b2c3e3b9f335cde7),platform=Linux 4.4.0-127-generic x86_64)

Had the same problem, I had to upgrade Chrome to the latest release and it fixed it.

Related

Unsupported Operating System and Failed to connect to MySQL

I am trying to install MySQL but I get the following warning:
I have a Mac and its installed the latest version 11.6 , so I don't understand why it says its not supported.
After that warning I tried to install a connection to MySQL server and I get an error:
I downloaded not the last version, but the second last and now everything it's fine. I know its not a "nice" solution but now I have no warning message and I successfully made an SQL connection.
The version I downloaded is:

LLDB remote debbuging between two macOS

I have been trying for hours to get a simple program to be debug remotely.
On the remote macOS, I cannot build it as it is an older macOS that cannot have the latest Xcode to build without any errors.
My plan was to build on the development machine, then use LLDB to debug it remotely.
On the remote machine I have run debugserver "DEV_IP:1234"
On the dev machine:
lldb
platform select remote-macosx
platform connect connect://REMOTE_IP:1234
file a.out
run
I do have this log on the remote machine Got a connection, waiting for process information for launching or attaching.
However, it always fails with the following error:
error: invalid host:port specification: 'REMOTE_IP'
If anyone has an idea on how I could remotely debug without having to install the binary on the remote machine AND without getting started before attaching as the process early crashes.

Execution error while trying to run Fiddler for mac

I've installed fiddler for mac and the mono framework. I also followed the install instructions pdf included in the download
While running
$ mono --arch=32 Fiddler.exe
I get
Thunderbolt
/Users/XXX/dev/fiddler-mac/FiddlerAttach.applescript:7:87: execution error: /bin/sh: Ethernet,127.0.0.1,8888,on,127.0.0.1,8888,on,0,0,off,0,0,off: command not found (127)
The UI does launch and when I try to start capturing traffic, the same error repeats in the terminal

XulRunner Not Compatible With SlimerJS on EC2

I'm trying to get SlimerJS up and running on my EC2 instance. I'm using an Ubuntu 12.04 LTS image. I installed firefox 41.0.1 and slimerjs 0.10.0pre. I have this working locally under pretty much identical circumstances. But when I try to launch this on the instance, I'm running into the error:
Gecko error: it seems /home/ubuntu/slimerjs-0.10.0pre/xulrunner/xulrunner is not compatible with SlimerJS. See Gecko version compatibility.
In the application.ini file, it says:
[Gecko]
MinVersion=17.0.0
MaxVersion=41.*
Which I seem to be satisfying. I can't figure out how to do this.

Selenium does not work when we get a upgrade from firefox

I am working on Automation tool Behat/Mink . After upgrading Firefox version to 25 , i am seeing this error .
Curl error thrown for http POST to http://localhost:4444/wd/hub/session/execute with params: {"script":"return document.getElementById('user') !== null;","args":[]}
Failed to connect to 127.0.0.1: Can't assign requested address
I am using selenium webdriver version 2.37.0.jar as the server.
Support for Firefox 25 has been added in version 2.38. Current version is 2.39 which supports Firefox 26.
It is a good practice to check for the new selenium version every time Firefox upgrades. Updating the server should work.
Official download page.
run this command before running your tests
java -jar selenium-server-standalone-*
this will help you to resolve your problem
make sure your selenium latest version should be on same folder

Resources