I'm using the Selenium WebDriver in R to parse some online data. I originally wrote the script a few months ago, and it worked great. However, I ran it again today and I receive the following error after running ClickElement():
Error: Summary: ScriptTimeout
Detail: A script did not complete before its timeout expired.
class: org.openqa.selenium.TimeoutException
I'm using Chrome as my browser, and have updated to the newest version (2.20) of ChromeDriver (I was using 2.19 when I wrote the script). This error is peculiar because it occurs pretty late in my script, after I have already used ClickElement() multiple other times. The element being clicked is a download button. Selenium completes the click and starts the download, but then throws the above error after a few minutes. At this point, the script continues.
I can only think of a few possible issues:
The ChromeDriver update has broken something. I've tried it with both 2.19 and 2.20, and I'm unsure how to test this further.
Some issue outside of my understanding of Selenium. From some experimenting and trying to Google similar problems, I've decided that it might have something to do with the download process itself, i.e. the driver freezes up because the download is currently running on the page.
I'm not sure what is going on, and I don't know enough about Selenium to troubleshoot it effectively. What can I do? I imagine that I'll need an alternative way to perform the download, or at least a way to click the element while ignoring the ScriptTimeout error. I receive the same error when I try to send the enter key to the element as well.
I have a similar issue but I can't figure out.
Try this after your clickElement code
Sys.sleep(2)
Related
I am using Selenium to scrape the data from web. However, when I try to run the Chromedriver it seems to run fine but no data has been extracted when I look into the csv file I export in the last. Additionally,when I time sleep the algorithm for 5 seconds and do right click + inspect it seems to work fine? Anybody knows what could be the issue and how can I fully automate the process without requiring the user to right click + inspect?
I am having massive trouble with using vpython in jupyter notbooks. I'm creating small animations with vpython. After a couple of minutes when I try to run a cell, it will either not show any output or will yield a error message "object could not be called".
The only fix I found for this is to restart or change the kernel. Most times it works then for the next few minutes until it stops again. This is really annoying and prevents real progress.
pictrue of error message with example code
all used objects have been imported in another cell before this one.
I am running vpython 7.3.2 and anaconda navigator 1.6.10 on a mac with High Sierra. As a browser I use Chrome.
Thank u for every hint to fix this permanently in advance!
Cheers,
Gordon
Try asking your question on the vpython forum and perhaps provide a sample notebook on github where with instructions on how to reproduce the problem.
https://groups.google.com/forum/?fromgroups&hl=en#!forum/vpython-users
Here is a link to demo vpython notebooks running in the cloud using binder service.
https://mybinder.org/v2/gh/BruceSherwood/vpython-jupyter/master?filepath=Demos
If you provide a notebook on github that demonstrates the problem then it should be reproduceable when running on mybinder.
https://mybinder.org/
It's an aspx web site. It's Huuuge. Oftentimes, we won't see errors until building the entire site. But it's always told us where the error is.
This time, I'm getting an Object reference not set to instance of an object. error with file, no line, no location. Double clicking on the error just does... nothing.
Error 3 Object reference not set to an instance of an object.
I've tried a few things that I've found here and elsewhere but nothing seems to be helping out or giving me more information. I've tried change the verbosity of compiler/build messages but those goggles don't seem to help.
Edit: Very specifically, the first time I try to build the site after opening the project, it says it builds just fine. Trying to build it again causes the error. Closing VS (2013) and reopening the project allows a first time build success and subsequent builds are failures. It should also be noted that it's not actually building anything because it completes far far too quickly - almost instantly.
Can anyone give me some ideas on how to track this down?
It turns out that the VS installation is completely broken. Banging on the keyboard like a monkey and then trying to build succeeds when it should not.
So I'm working on my Meteor project and all of a sudden everything stops working and my console reports that everything is 'undefined'. See screenshot. Why does this happen? Usually things will just randomly start working again after I reboot my machine or go get lunch.
This can happen if you have a hot code reload during when the page is loading from a previous hot code reload.
Your browser will eventually reconnect to the server, reconnect & refresh the page. In the case above it looks the the bit of Js that connects to the server doesn't get loaded to begin with (the DDP bit) so it doesn't behave as normal. If it reconnects it can fix it self by refreshing.
It's very hard to tell what exactly is causing it from the information you've given. I'd look at custom packages that replace core packages or some kind of of package you have that runs early on in your code that would stop the normal loading of a project.
If you're using meteor on windows there are a couple of bugs that do this too. I'm not sure how to get past those besides doing Ctrl+C to stop and then using meteor to start the project again.
I am writing test with the selenium and I export to phpunit.
But click command doesn't work for me. I am writing like that $this->click("css=input.login");. But it shows errors like that ERROR: Command execution failure. And I already tested mine element correct or not.
I can find it from this. And the answer is the following.
This might also be related to a Selenium bug with the recent Firefox release (FF 22 I think), see (will be fixed in Selenium 2.34).
See Details in here.