We Keep Coding

APPIUM: Cannot bind listener: cannot bind to 127.0.0.1:8200

Suddenly I’m Facing this error when I try to run appium.
Error:
An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\vsingh\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward tcp:8200 tcp:6790’ exited with code 1’; Stderr: ‘adb.exe: error: cannot bind listener: cannot bind to 127.0.0.1:8200: An attempt was made to access a socket in a way forbidden by its access permissions. (10013)’; Code: ‘1’
desired Cap:
{
“deviceName”: “myphone”,
“udid”: “emulator-5554”,
“platformName”: “Android”,
“platformVersion”: “9.0”,
“appWaitActivity”: “com.application.activity.MainDrawerActivity”,
“appWaitPackage”: “com.application.pas”,
“noReset”: true
}
Tried adb kill-server, adb root. but still no effect.
It was working fine till yesterday.
Using Appium Inspector

Most likely port is left in-use.
Try running sudo lsof -i | grep 8080 or nc -l 0.0.0.0 8080 on machine terminal, whatever works to see if port in use.
If it is in use, then stop the process. The best way to avoid it in future is either create cleanup scripts to free all required ports before you start tests again or run tests in docker container.

How to kill process in robotframework

i am trying to kill process in robot framework, although the log says that process is killed , i am still able to see the command prompt invoked by the process Library.
is there anyway to kill the invoked command prompt in Suite Teardown ?
*** Settings ***
Library Process
Suite Setup Generic Suite Setup
Suite TearDown Terminate All Processes kill=True
*** Test Cases ***
login
*** Keywords ***
Generic Suite Setup
#This is invoking cmd
#when i run this , got error as mentioned below
Run Process appium -p 4723
Run Process appium -p 4750
#I tried to include cmd , no error but can't see the cmd getting invoked
Run Process cmd appium -p 4750
My python version :2.7.14
pybot version : 3.0.2
After removing start & "cmd" i get the error
Parent suite setup failed:
WindowsError: [Error 2] The system cannot find the file specified
Appium path is set in environment variables

When you use Start Process, each argument that you would use on a command line needs to be an argument in robot. For example, if you would type appium -p 4723 on the command line, then in robot you would do:
Start process appium -p 4723
(note: there are two spaces between "process", "appium", "-p", and "4723")
When you do this, robot will look through the folders in your PATH environment variable in order to find a program named "appium" (or "appium.exe" on windows). If you get the error "cannot find the file specified" that usually means that the program you're trying to run isn't in a folder in your PATH. It could also mean that the program isn't installed, or that you misspelled the app name, but I'm assuming neither of those are true in this case.
The simplest solution is to find where the appium executable is, and then use the full and complete path as the first argument to Run Process (eg: Run Process C:/the/path/to/appium.exe -p 4723)

PyCharm/Python. Code doesn't run. Immediately receiving "Getting Process finished with exit code 0"

I recently switched my workstation and reinstalled all my environment on Fedora 25.
When attempting to run any part of my project (I run PyTest tests) I always end up getting "Process finished with exit code 0" message in debug.
Here's the full debug message:
/usr/bin/python2.7 /usr/share/java/pycharm-community/helpers/pydev/pydevd.py --multiproc --qt-support --client 127.0.0.1 --port 46537 --file /home/pavel/Documents/integration_tests/cfme/tests/containers/test_containers_default_project_replicators.py
warning: Debugger speedups using cython not found. Run '"/usr/bin/python2.7" "/usr/share/java/pycharm-community/helpers/pydev/setup_cython.py" build_ext --inplace' to build.
pydev debugger: process 10166 is connecting
Connected to pydev debugger (build 163.10154.50)
/home/pavel/Documents/integration_tests/utils/log.py:222: UserWarning: clearing configuration is bad
del(conf['env'])
The project I am trying to run is actually open sourced and is here for reference:
https://github.com/ManageIQ/integration_tests

Ok, so the problem was that the I tried to run it as Python Run/Debug configuration instead of Py.test run/debug configuration.
From
How do I configure PyCharm to run py.test tests?
Please go to File | Settings | Tools | Python Integrated Tools and change the default test runner to py.test. Then you'll get the py.test option to create tests instead of the unittest one.

In my case, along with the rest of great suggestions, somehow content root was not defined.
Solution: File|Settings|Project Structure -> Add Content Root (Here you select your project folder)
*It took me a looong time for this, hope that this will help somebody :)

Opening a terminal application from python and running custom scripts inside it

I'm working with a software called dc_shell that has a terminal command (also called dc_shell) on a CentOS Linux server. when I run dc_shell command, I'm connected to its terminal and I'm able to run scripts/commands inside it. (This is all done manually)
So the real problem is that I want to do this task all from a Python program. Meaning that I have a Python code which does some task, and after that has to open dc_shell and run some commands inside it.
I have used subprocess.Popen before and this doesn't have any problem when I run commands like ls or other general terminal commands. But when I run dc_shell command it seems like it crashes and nothing happens, and when I try to terminate the session I get the following errors in my terminal.
Here's my code:
def run_scripts():
commandtext = 'cd ..; dc_shell-xg-t; set_app_var link_library "slow.db"; set_app_var target_library "slow.db"; set_app_var symbol_library "tsmc18.sdb";'
print(commandtext)
process = subprocess.Popen(commandtext,stdout=subprocess.PIPE, shell=True)
proc_stdout = process.communicate()[0].strip()
print(proc_stdout)
and the output is:
cd ..; dc_shell-xg-t; set_app_var link_library "slow.db"; set_app_var target_library "slow.db"; set_app_var symbol_library "tsmc18.sdb";
and nothing happens... and after terminating I get:
[User#server python]$ /bin/sh: set_app_var: command not found
/bin/sh: set_app_var: command not found
/bin/sh: set_app_var: command not found

Do you need to use dc_shell to run your commands?
If so, that should be your executable and the rest of commands your arguments.
You should never use shell=True due to security considerations (the warning in the 2.x docs for subprocess seems much clearer to me).

Python Fabric error when executing git archive command

I'm running Fabric on a windows 7 machine, when I type:
fab production setup
I get the following error:
[localhost] run: git archive --format=tar master > 20110221142115.tar
Warning: local() encountered an error (return code 1) while executing 'git archi
ve --format=tar master > 20110221142115.tar'
the fabric file works fine on my Windows XP machine, but I can't seem to get past this error. I also tried running the "git archive" command from the prompt, it works fine no issues. Any idea why Fabric is puking?

If the same script/command works on Windows XP, then did you check if Windows 7 firewall or any sort-of-protection is not allowing your connection to go through? Try if the following works on interactive prompt:
from fabric.api import local
local('git archive')