We have quarantine mode enabled in our .testcaferc file. We've just started implementing visual testing with applitools, but because of how the checks work with applitools, when quarantine mode is enabled, we're wasting checks on failing tests.
We want to run our visual tests with a script that would overwrite some config key:values, but haven't found documentation on how to disable quarantine mode via CLI.
I've tried -q false, -q=false, --quarantine-mode false, --quarantine-mode=false.
We can't set attempts or success to 0 as they need to be > 0 and attempts needs to be > success.
The only other option I can think of is to create a whole separate config just for visual testing, which we find to be a tad unneeded when a script is much easier.
Can anyone shine some light on how a CLI command can be written to disable quarantine mode?
It isn't implemented yet. As a workaround, you also can delete the quarantine option from the config and assign it with CLI only for the required tests. We will inform you in this issue once it is implemented
Related
Introduction
I've looked around and haven't seen anyone else having my issue.
Basically, I am wanting to run a start.bat file to start up my server before I start up my debugging session. I currently have my debugging inside of an IntelliJ Configuration and it works well. The problem is that in the options for my configuration I can't seem to add an "External Tools" task to the Before Launch section. I was able to add a maven task here previously. However, when I follow the following steps, the "start.bat" is not added.
First I go into Settings->Tools->External Tools to add my Spigot-Server tool which basically calls the start.bat file inside of a test-server directory.
Snippet of External Tools
Second, I go into my "Debug Spigot" configuration and at the bottom, I see a "Before Launch" Section.
Snippet of Spigot Debug options
I click on the + inside of that section to add a new task, and I click on "External Tools"
Snippet of adding External Tools Task
And then I make sure my Spigot-Server task is selected.
Snippet of select external tool
And then once I hit okay, the window closes but I don't see a new task added to the before launch section. It looks the same it did before I clicked on anything. I also don't see any status message at the bottom of IntelliJ
I basically expect the task "Spigot-Server" to show under the Before Launch section. This would basically start up the server and once the server was completely started, it would then launch the debugging configuration.
I think it may be an issue with IntelliJ's UI. I searched IntelliJ's issue tracker But couldn't find any that matched.
I'm wanting to know if there are any work arounds to get this setup in IntelliJ>
I was able to achieve my goal by doing some workarounds that I discovered with the help of CrazyCoder. I found this stackoverflow question that told me about the batch plugin.
I was able to create a Batch run configuration for a wrapper batch file that gets around the limitation CrazyCoder mentioned. He said that even if I did get my setup where my server runs before my debugging is launched, my debugging would never launch. This is because the terminal process needs to exit before the next task starts.
To get around this this is the wrapper batch file I created.
#echo OFF
START "Spigot-Server" /D C:\Users\rocke\Documents\Programming\Minecraft\Spigot\capture-the-carrot\test-server "start.bat"
ping -n 3 127.0.0.1 >nul
It basically uses the "START" command to run the task asynchronously and then waits 2 seconds. This is because all I need to do is wait for the start.bat command to run the very first part so that it establishes remote debugging. And then the wrapper ends after 2 seconds (the 3 represents the number of seconds I want to wait +1). And this allows the Debugging process to start while also ensuring that the server has setup remote debugging!
I'll just share screenshots of my configuration if anyone wants to do the same.
Maven Build Configuration
Spigot Server Start Configuration
Remote Debugging Configuration
The way this is setup is once I run the Remote Debugging Configuration, it has a "Before Launch" Task of Spigot Server. Spigot Server also has a "Before Launch" Task of Maven Build Project.
So my Maven Build Project runs, then my Spigot Server wrapper runs and after 2 seconds terminates, and then my Debugging Configuration runs!
If you have any questions regarding remote debugging with spigot, use this resource: https://www.spigotmc.org/wiki/intellij-debug-your-plugin/
Symptoms:
Starting parcel watch completes the initial build, the command continues running but doesn't detect any further changes
Context:
Parcel is being run from an IntelliJ IDEA platform IDE (Rider)
Safe-write functionality is disabled, so I am completely sure that the file is actually being changed on disk
Problem is reproducible when I edit referenced CSS or JS using a different editor (vim)
OS is Ubuntu Linux
Why aren't subsequent changes to files detected by Parcel, triggering a re-build?
FWIW, you can set up a file watcher inside intellij that runs touch on the file. Just make sure it doesn't trigger on external file changes, or you'll loop forever. This way, you can leave safe write on and still trigger parcel and other external watchers.
IntelliJ-based IDEs have a habit of completely burning through the inotify limit. In my case, setting fs.inotify.max_user_watches in /etc/sysctl.conf to a higher value (524288 in my case, in accordance with the instructions given by JetBrains) and then running sudo sysctl -p --system before restarting parcel watch solved the problem conclusively.
I am trying to diagnose a few issues with ssl connectivity with Leingen. I am trying to find what SSL Key Store and Trust Store is being Used by Leingen,
I am behind a corporate firewall and we have self signed certificates deployed on all our desktops . I am running lein.bat on a windows 10.
Hence I have to start Leingen with java -Djavax.net.debug=true option.
The :jvm-opts in the project.clj wont work -- I need to make sure the Liengen's JVM is started with this option
You can set leiningen JVM options by setting LEIN_JVM_OPTS environment variable before running lein in the same terminal session.
The lein command is just a shell script which eventually invokes java with various options. You can edit this script to see what options are used and/or to modify them.
As Piotrek mentioned, the LEIN_JVM_OPTS environment variable is the canonical way of passing options to the jvm in which lein runs. You can see it used on line 372 of the source code.
For your case:
> export LEIN_JVM_OPTS='-Djavax.net.debug=true'
> lein clean
> lein run
Since you're running windows, you'll want to actually look at the lein.bat file. You'll still need to update LEIN_JVM_OPTS, but how you go about it will be a bit different. If you're using windows command terminal (cmd.exe) you will want to use the set command.
set LEIN_JVM_OPTS="-Djavax.net.debug=true"
The command is likely different if you're using powershell, and you can likely find out how to set that on this page on environment variables.
Can we disable WebRTC in CEF 3 ?
I`m referring specifically to JavaScript access to local ips.
Chrome seems to have settings like chrome.privacy.network.webRTCMultipleRoutesEnabled that help - but these do not seem to exist in CEF.
I had same problem and ended up rebuilding CEF and Chrome without WebRTC support. Here is steps, which I use:
Download automate-git.py script in c:/code/automate folder from here: https://bitbucket.org/chromiumembedded/cef/raw/master/tools/automate/automate-git.py
Create batch with following content and run it:
SET GYP_MSVS_VERSION=2015
python c:/code/automate/automate-git.py --verbose-build --download-dir=C:/code/chromium_git --branch=[REPLACE WITH CURRENT BRANCH] --minimal-distrib --no-debug-build --force-build
pause
Set enable_webrtc to 0 inside C:\code\chromium_git\chromium\src\build\common.gypi file.
Run batch again.
And maybe there there is easier way, for example, using CefRequestContext::SetPreference.
I am using the latest (2014-01-03) Golang plugin for IntelliJ - for the first time.
Usually, my terminal workflow is to do go build && ./executable -args=1
So I am attempting to create a launch configuration to do the same thing, I took these actions:
Create a "Go Application" configuration
Fill in GOPATH/GOROOT environment variable
Fill in CLI arguments
Because there has to be a file to run, so I chose the one with func main()
Then there is a problem. When I run the configuration, the Golang plugin does not build the project, but instead builds the single script file with main method, then attempt to run it - obviously it does not work.
How to create a configuration equivelent of go build && ./executable -args=1?
Try to use the latest version from the official plugin manager.
If that doesn't work, please help us identify the issue by submitting a report here
Also, we are working hard to update the plugin with better type checks, debugging, go appengine support, improved formatter and much more but any help in improving the plugin is greatly appreciated.
Hope it helps.
However, I prefer to use goclipse which support auto-build, auto code completion and debug.