When trying to code in google colab, the code completion works really slow. Anyone knows how to fix this?
I would say it takes about a good "1 and a half" to 2 seconds before any suggetions are made.
Workflow = super ruined
Running colab on chrome.
Found a way to fix it.
In colab press tools -> settings -> editor -> scroll down -> "Code diagnostics" -> turn it off.
Fixed my problem.
Related
I'm using Arena simulator (by Rockwell), in particular the "Arena training and Evaluation Mode" for students.
After using it without any problems for a few months, since yesterday every time I click on "check model" or "run the model" Arena closes automatically. I have no idea what could be the cause (I haven't made any changes to the PC, the only thing I did was to add a new video card).
Has anyone had the same problem? Any suggestions?
Arena works with access software, it is likely that the version of access you have on your computer is not compatible with the version Arena needs to work properly.
Go to the unzipped folder you extracted from the zip you downloaded, go to MediaImage, then Redist, then AccessDataBaseEngine and finally install the file found there.
These steps should solve your problem.
I was having the same issue and what I did to fix it was reinstalling. The only thing I made differently this time was to tick on the "repair" option rather than "update" when prompted with the access runtime window.
Hope this helps!
i had the same problem and it worked.
installed a file called "AccessRuntime_x64_en-us"
Thanks for the solution:)
Fix in a few seconds: Just double click on the .accdb file in the same folder as you simulation file and click open on the pop up screen. Then try running your model. İt will fix it.
For details check the link below.
https://youtu.be/V7KvyRtMiho
I started using Colab notebook but I found out that it doesn't accept Control+F shortcut(On google chrome) to move right.
I sure deleted shortcut that was using control+F.
Still doesn't work.
Has anyone solved this?
Thank you
UPDATED: Now you can have it in a new version of editor.
I'm struggling with this as well on all machines that I tried. There is a broader ticket on github's colab page.
As a temporarily workaround I'm applying my to-go swiss-knife Better Touch Tool and make a custom shortcut for this.
For related issues (like 'B' for adding cell below, for instance) you can remap that in Tools -> Keyboard shortcuts.
Hope it helps.
Apologies if this belongs on a different stack exchange site.
Using Intellij Ultimate v 2017.1.1 on OSX Sierra, when I do a search in file, using CMD+f, I get an unusable full screen search dialog. Has anyone seen this ? Images attached.
Before clicking CMD+f (all is well)
I try to search for something:
Any help appreciated. The Internets has so far yielded no help.
This issue is already fixed, please see https://youtrack.jetbrains.com/issue/IDEA-170295 for details.
It was caused by the Swing MigLayout misbehavior when system DPI was extremely high.
This can happen if you accidentally paste a huge block of code into the finder, try CMD+f and then CMD+a and finally delete.
I have just started using Selenium IDE and I am trying to open the Google search engine and type in a sum (example 5+7). This will open a result page with a calculator and the answer in it.
So far the test works but when I try to verify that the answer is correct I am getting an error even though it is. Basically I am highlighting the answer, right clicking on it and clicking verifyText. Similarly if I click on the text box holding the answer and choose verifyElementPresent I get an error as well.
Can someone please enlighten me on why I am getting these errors.
P.S I am new to Selenium so I would appreciate it if your answer is kept simple
Thanks in advance :)
You are getting the error because of the latency time.
Just add a waitForElementPresent keyword before validating the result.
It Workss...
Happie learning. :)
I am executing a simple recorded script in Selenium , in which i just search a page in Google and then click it , but when Run that recorded script it is giving me the "Error [error] Element link not found".
And following is the Script which i am running,any help would be very useful.
New Test
New Test
open
/
type
q
Bill Gates
click
link=Bill Gates: Chairman
click
link=Bill Gates: Chairman
I got the same error message while going through the tutorials online. I found out that the scripts were running too fast for FF to load the links. If you slow down the playback by moving the green button on the Fast-Slow bar to somewhere in the middle the scripts run without any errors.
I guess I know the answer. It might be bcz of any javascript error(you can see that on the status bar at the
Right corner(IE)) or that link element might not be placed correctly in the box(box model).
Here you can use
Selenium.focus("link=text")
:selenium.keyPressNative("10") . It presses the enter key.but while selenium is executing this statement
Do not change the focus from your AUT (don't touch the mouse).
In IDE ,just paste the above statement on click().
Well, I don't think you have to slow the speed down. You know the problem is caused by clicking on the link before it is available, so you could add an extra command waitForVisible (e.g. link=Bill Gates: Chairman) before the clickAndWait command.
Im assuming you are using Google instant as there is no "click search button" command, the link is probably not preset because selenium is not waiting for Google instant to respond or the javascript to render the link. If you manually add in a click command to search it should solve it.
My solution is almost the same as Cuongs. Though I change the speed by using a command and change it back afterwards.
Before you click the link, you can set the speed to slow:
Command: setSpeed
Target: 3000
You can change the speed afterwards again to ~1000
I also had same problem. I did two things which fixed the problem. I changed the speed in Selenium IDE from fast to slow (located at top left of IDE), and I minimized the IDE after hitting play button. I guess for people using only one monitor, minimizing Selenium IDE would help the test find the thing it is looking for; for ppl with two screens, opening Selenium IDE in one screen, and opening browser in another screen would be best.
Info: Installing this plug-in (Selenium IDE: Flow Control) fixed lots of unexpected errors for me while playing with Selenium IDE:-
https://addons.mozilla.org/en-US/firefox/addon/flow-control/?src=dp-dl-othersby