On monkey Wiki : "Greasemonkey will check periodically for new versions of the script by downloading it". But what does it mean? Once a week? Twice a hour?
Anyone have real numbers?
While Hellion does point to the original post when auto-update was released in early 2012 this hasn't been true for some time. It isn't documented anywhere so we have to do some digging. You can see here Greasemonkey uses what looks like a built in Firefox mechanism to check and update. It is hard to tell when though. I know from experience that this is in fact a lot less that every 7 days. I have had it happen within an hour. Restarting firefox doesn't seem to trigger it but the shortest I have seen was within an hour. Furthermore if we search about:config in Firefox for update we can find a particular setting that kinda stands out. extensions.update.interval;86400. Obviously this is saying the extensions update interval is set to 86400 second (24 hours). Since Greasemonkey is tying the update process to a firefox update process I would think this is it. I will try changing this setting to see if I am right. Later this weekend when I am done with this userscript I am working on I will let you know what I find out.
Although this question is toward Greasemonkey I will go ahead and say Tampermonkey (Chrome) is much easier to check. Just click on the Tampbermonkey icon > Dashboard then go to settings and you can see check interval is set to 12 hours or whatever you changed it to.
According to http://www.greasespot.net/2012/02/automatic-script-updates-come-to.html,
By default updates will be checked for every seven days, and automatically installed when found.
Related
Currently Jest in my VSCode uses the --watch parameter (I use the Orta.vscode-jest extension), which mean when I save a file, it will run all tests in uncommitted files.
It's a good default behavior but sometimes my upcoming commit may imply multiple files and I don't want to waste 75% of my time and resources on tests I don't to focus on.
After reading documentation, I found I can turn off the auto-run (see arrow below), so now when saving nothing happens, and I was expecting a way to trigger manually the test I want.
Unfortunately once done it's like if the extension was totally shut down. See below, I have no longer the ability to run tests through the extension.
Do you know a way to solve this? Keeping icon buttons to trigger manually specific tests?
I saw some homemade solution https://stackoverflow.com/a/55279902/3608410 (see Running a selected Jest test in Visual Studio Code) but I feel it's weird since we have a powerful extension already installed.
(maybe I missed something...)
Thank you,
Didn't see that before but if doing a right click in the test file where needed, in the menu I'm able to run a specific test, handy!
AVG always wants to do a 15 second scan on files it doesn't trust. As a result I get this error when the setup begins.
I can click Ok and eventually the setup will continue.
Is there any way to make this a more friendly user experience? I know I can get my setups added to whitelists But I am referring to this 15 second scan and the message shown to the user.
Infact, when it continues (when being run from Inno) I then get:
I found a interesting user discussion on the AVG website. In short, one of the users stated:
Hello, I found the problem, and its pretty easy to fix. Go to the
"Settings" option in the menu. In the "General" section there is a
tick box for "Enable CyberCapture" - untick it.
CyberCapture just checks programs that are not run a lot, which means
if you recompile a program then it "looks" different to AVG, which
means AVG things it has not been run a lot, ie its a brand new
program, so AVG always does this CyberCapture check on newly compiled
programs. Unticking the "Enable CyberCapture" fixes the issue. No need
to repair or reinstall anything, it would be nice if the AVG
representatives at least had some knowledge of the "General" settings
for AVG, that would have saved some time.
I am actually using AVG 19.5 the option was found here:
I can confirm that switch this off stops these warnings I was getting.
Intermittent Failures with webdriver.js
I am creating some webdriver.js* scripts to automate some time consuming test setup activities. However, when I run the script and do other things with my keyboard and mouse, I come back and find that, intermittently, a particular element cannot be found. And it's a different element each time.
When I run the same scripts and just watch them run, the scripts execute correctly.
Also, when I researched this potential problem, I came up with lots of stuff on using the mouse in webdriver scripts and problems with the click method itself but couldn't find anything to do with my issue. So I'm wondering whether I'm just doing something wrong here.
So What's The Question?
My question is: Is webdriver.js not meant to run like this? (that is, run locally while the keyboard and mouse are doing other things)?
Webdriver.py?
I don't remember having these problems when I used webdriver.py a few years back. iirc, I was able to run the scripts while the workstation was locked (via Win + L) though my memory isn't what it used to be ;)
I would use webdriver.py, however, no one else in our team knows python so I thought I would go webdriver.js since we all know javascript :)
Params: IE11, Windows 10.
* Also, when I say "webdriver.js", I mean the webdriver that is installed after following the steps here
I found that if I replaced the .click() calls with an equivalent .sendKeys() call (e.g. webdriver.Key.ENTER / webdriver.Key.SPACE) , this would get around the problem. I could even lock my workstation and the scripts would run without any problems.
If I do "Reconcile Offline Work" in P4V, after a while the reconciling will finish and a window will eventually pop up showing the files that were modified, added, or removed. Sometimes I know the reconciling will take a few minutes or more based on the huge number of files in the directory, so I move on and start working on something else, and I expect that the reconciling will be done when I return later. However, sometimes, when I go back to P4V several minutes later, I see the window filled in with all of the modified, added, and removed files for a brief moment before they get blanked out and the scan seems to start all over again.
This can be quite aggravating since I'm trying to avoid having to sit around and wait for the reconciling to complete, but I end up having to wait for multiple reconciles when I only want to do it once.
Any ideas as to what causes this or how to turn off this repeated reconciling when I only want to reconcile once?
I'm using the "2014.3" version.
I did a bit of additional searching on this and finally stumbled upon the answer!
This is bug #70465: https://www.perforce.com/perforce/doc.current/user/p4vnotes.txt
#1171326 (Bug #70465)
There is now a preference to disable global refresh affecting the Reconcile
Offline Work dialog. Default is to continue allowing global refresh to
update the dialog. The preference can be found on the Behavior page in
preferences.
Updating to a newer version (2015.1 or newer) will allow me to disable the global refresh in the Preferences/Behavior menu.
So I am using the omnibox in my extension, and after a user enters something in the omnibox, it becomes part of the extensions "history" (which would be a nice feature). However, when the history entry is clicked on, it goes to "chrome-extension//?q=, and that returns an Error 6 (net::ERR_FILE_NOT_FOUND). Is there any way to remedy this situation, either by allowing this to act as it did the first time, or just by disabling the history?
EDIT: so it turns out one cannot inject content scripts into chrome-extensions (even though the documentation says you can (they're fixing this hopefully)
Any other advice is still appreciated, but I've become less hopeful that this can be done.