When I am trying to run the command rasa run actions & rasa shell in the terminal for running rasa actions file, my terminal is freezing and the endpoint server is not starting. The terminal freezes at this point:
(rasa2) C:\Users\nabaj\source\repos\rasa2>rasa run actions & rasa shell 2020-07-17 16:52:26 INFO rasa_sdk.endpoint - Starting action endpoint server... 2020-07-17 16:52:26 INFO rasa_sdk.executor - Registered function for 'action_check_search'.
Have tried it multiple times and even on different systems but the issue still persists.
snapshot of the terminal
The problem has been solved. I ran rasa run and rasa shell in two different terminals. It worked. For more reference check this rasa forum page
Related
There is a way to run CI of GUI testing in bamboo agent as service on windows server?
I don't think it is possible, just run the bamboo agent as a proccess.
I am using puppeteer as libray to run the GUI testing on electron app.
any type of another solution will help :)
If you can achieve running the build via PowerShell or cmd prompt, you may do so with a script task.
For this, you have to make the agent run as a local user as explained in this page. This way, you have the same environment as the local user and the commands to execute your electron app will work successfully.
Im currently working on a deployment process that is working fine until the last stage.
I have Jenkins installed on my debian 10 machine. I have a git project with a Jenkinsfile inside.
All stages are working fine.
My problem is now, that I want to start a session with Jenkins with the screen command, the session is now created (detached) and after that the pipeline will finish, the session doesnt exist anymore.
To create the session I use the following commands:
screen -S server ./start.sh
-> That will tell me: Must be connected to a terminal.
Then I tried this command:
screen -dm -S server ./start.sh
-> Here the session will be created and then removed after Jenkins is finish with the pipeline
I found the following solution that is working fine for me:
sh 'JENKINS_NODE_COOKIE=dontKillMe ./start.sh'
That will run my bash script with the screen command
I've started experimenting with Composer Scripts.
I have a project where there are "Functional tests" of the API endpoints. Running the whole test suite requires running the following commands in order:
composer install to install all required dependencies of the backend APIs
php yii server --test to start a lite server that is connected to the "test" MySQL database. The test server starts running on localhost:9000.
sh vendor/bin/phpunit --configuration tests/functional/phpunit.xml to run th actual tests. This last command triggers the execution of all test cases, most of which execute HTTP calls to the lite server, launched at step 2.
I would like to automate and "atomize" this 3 step process into a single Composer script that can be easily started, killed and restarted effortlessly.
Here's my current progress:
"scripts": {
"test-functional": [
"#composer install",
"php yii server --test",
"sh vendor/bin/phpunit --configuration tests/functional/phpunit.xml"
]
}
The problem is that the 2-nd command (php yii server --test) "steals" the terminal because PHPs built-in lite server requires the terminal to be open while the command is running. Killing the command kills the lite server as well. I tried suffixing the second step of the script with & which generally makes processes go in the background and not steal the terminal, but it seems this trick doesn't work for Composer Scripts. Any other workaround or possibility that I'm missing?
My final goal is to make the 3 steps execute in an atomic way, output the results of the tests and end the command, cleaning up everything (including killing the lite server, launched in step 2).
I develop my python applications with Pycharm and I love it. Recently, I discovered grunt and the superb watch-action of grunt.
I want to start grunt watch, and maybe some other applications, in the background when I start my Django server using run. I know, how to start applications before launch but Pycharm waits for their exit before starting the django server. So this is not the right way, because I need the application to run in the background.
Any ideads how to achieve this?
You can setup an external tool as a launcher for the background task.
I am currently on mac, hopefully you can adapt the idea with some dos commands. Let's assume the background task can be started from task.py
Step 1: Create a "launcher script", saved as bg_run.sh in this example. Note the fork instruction & to run the task in a new process.
run_task() {
python /Path/To/Task/task.py
}
run_task &
Step 2: Create an external tool in Preferences | Tools | External Tools to run that script.
Step 3: Add that external tool to run before launch in the Run/Debug Configurations.
Note: The question on how to kill that background task is left open ;)
I've successfully run IOS UI Automation Instruments from command line on my local Mac. When it starts to test, the simulator will automatically pop up and then do the stuff.
However, when I SSH to a build server (with OSX and xcode, will use Jenkins eventually) and try to do the same thing, it doesn't work well.
Building process is fine, but as long as I run instruments, the terminal will then hang there without doing anything. I figure it has something to do with iphone simulator GUI but since it's CLI, I don't know what's going on...
Do you guys have any idea? Thanks!!
.
After executing the command from Jenkins through SSH; in most cases you would see a pop up window as in the screen shot. You will have to get past this screen to execute your tests. This post addresses how to get past that issue Stop "developer tools access needs to take control of another process for debugging to continue" alert
I've had the same issue. instruments -w "$DEVICE" were ignoring parameters.
Same with
DEVICE_TARGET='iPhone 6 (8.1 Simulator)' cucumber --format json -o test-reports/cucumber-8.1-iphone.json
It were ignoring DEVICE_TARGET parameter.
Solved via running Jenkins slave NOT as a SSH slave but as the Slave agent via java web start
http://i.stack.imgur.com/lNlPA.png
As i understand this issue is caused by OS X launchagent that managing sshd and performs scope of restrictions for remote users.
IMPORTANT! Slave agent should be started from OS X desktop, not via ssh! I've connected via VNC and launched slave java web agent on the OS X UI terminal.