It is a conundrum, yesterday my chromedriver automation worked as usual.
Today, it pulls up the cromebrowser, and remains blankscreened, with
data:,
as the URL.
This used to happen with capy/chrome but the URL was
about:blank
Why would this stop working all of a sudden? Is this happening to anyone else?
What we believe happened is that something we did on our system didn't sit with the old version of chromedriver we were using.
Changing to v2.8.241036 fixed the issue.
Related
I'm testing my Rails project and there are some problems when the test is running.
cucumber features/test.feature
I have installed chromedriver for WSL2 and the test can run fine. However, the browser showing up is not rendered at all, it only has a border and transparent body like this.
I can still open google-chrome and it is displayed correctly. And the project used to work on WSL1. I can also take screenshots when testing, it's just that the browser's UI is not rendered.
I have installed the driver for GPU as stated in the WSL guide but the problem still persisted.
Has anyone encountered this problem and how can I fix it? Thank you very much.
I got a task to update a URL in a test (using Selenium, Java and Chromedriver) to a new URL. The page is the same, just at a new location. This test worked fine with the old URL.
I brought up an instance of Chrome and verified I could access the URL.
Then I changed the URL, committed to git, and ran on our Jenkins machine and it failed. The screenshot said "This site can’t be reached". I told a co-worker that I think the URL must be wrong (though it worked on my desktop without Selenium). He tried it and it loaded fine. I tried it again from a regular Chrome window and it loaded fine. I tried from Eclipse using Selenium and I got the message about the site could not be accessed.
So I ran Eclipse, stopped it right when Chrome came up but hadn't loaded a URL yet. I manually entered the URL (from copy/paste) and got "This site cannot be accessed). Then I brought up a regular Chrome window and pasted the URL in and it loaded fine.
I decided to look for differences. So in my regular Chrome window it was "Version 77.0.3865.120 (Official Build) (64-bit)". I did the same on the version running under Chromedriver and got "Version 77.0.3865.120 (Official Build) (64-bit)". So the same.
I did a search for the latest Chromedriver. It said for version 77 to please use 77.0.3865.40. This was not what I was using. So I downloaded the correct version and thought "surely this will fix it". I verified it was 77.0.3865.40 coming up. But, as you guessed it, I got the same problem after updating to the most compatible Chromedriver.
Some searches said that basically nothing would be able to tell, but there was one property that Chromedriver inserts. I don't know whether this would be enough to block a session using Chromedriver?
The only thing I can think of is that we have iBoss and possibly iBoss is blocking it? Either that or somehow the site is blocking it.
I would like to share the URL with you but I do not know whether that would be violating company policy. If I get permission, I will share the URLs.
by the way, the error is "ERR TUNNEL CONNECTION FAILED"
Got some internal help to help fix some settings
I'm just curious - have any fellow Neo4j-ers ever encountered this behavior?
Right now, I've got 30 queries in the 'Saved Scripts' part of the Neo4j browser interface. When I try to save another, it will remain there until the the page is reloaded/refreshed - it then disappears.
I thought that 30 might be some soft limit determined in a Neo4j configuration file (/etc/neo4j/neo4.conf) but I can't find any statements in the file relating to this. If it's at all pertinent, I'm running x64 CentOS 7 as a VM - this is where my Neo4j has been configured. I've checked the debug logs and I don't see any warnings or errors relevant to this issue.
Is this behavior normal? If so, is there a way to change it?
I solved the problem. Just needed to reboot the VM apparently.
Still not sure what the root cause of this is - but rebooting was, in this case, the remedy.
I am using umbraco v 4.11.6 (Assembly version: 1.0.4834.19775) the issue is every time the server shuts down or restarts I need to republish the pages which are not loaded.
So please let me know the root cause for this issue if anyone knows or any other things that can be done to over come from this
Thanks in Advance
In version 4.6 there was an issue which had the same behavior when the SQL database was not available at boot time of the website. But with version 4.11 this should be fixed a long time.
I would investigate the logs (~/app_data/logs/). You might find some clue there. Append logs to your post if you can not find the issue.
This might be a problem with some ApplicationEventHandlers not running properly. Or with write permissions on the proper folders. Try adding more logs to the code, so you are sure what runs (and what doesn't).
If you can not find the answer, try the umbraco forums : http://our.umbraco.org/forum
We have a peculiar problem with logging in to django admin on our dev server - just surfaced today, sept 1st. When we try to log in using staff usernames and passwords we are returned the following message:
Looks like your browser isn't configured to accept cookies. Please enable cookies, reload this page, and try again.
We encounter the same problem on our local installations:
I was using django 1.1.1 upgraded to 1.1.2 problem with both returning same
Another developer encountered the same problem on a fresh 1.2.1 installation
I read a lot of chatter about setting SESSION_COOKIE_DOMAIN & SESSION_COOKIE_SECURE, we never had these set on any of our installations and never encountered any problems. We then specified the following in our local installations to no avail.
SESSION_COOKIE_DOMAIN = '127.0.0.1:8000'
SESSION_COOKIE_SECURE = False
This problem just appeared today, yesterday things were fine on local installations, cookies are enabled on all our browsers.
Any one experiencing the same? any suggestions?
It turns out it was a simple cookie problem using chromium-browser---my profile was corrupt--- which started an escapade of changing settings.py and other things, which broke other browsers etc.
Ah well, solved now.