I am trying to debug a ROS node inside VSCode but it seems that the debugger is not working. Please see below screen recordings:
Attaching a running node
Launching nodes
I noticed that attaching a node is requesting authentication. But after providing the correct password, nothing happens. Similarly, the launching nodes show processes for a second but die/disappear immediately.
Below is the version related information:
Visual Studio Code v1.74.3
VSCode-ROS Extension v0.8.4
ROS Melodic
GCC v7.5.0
Python v2.7.17
Ubuntu OS v18.04.6 LTS
Ubuntu OS Kenel v5.4.0-137-generic
The developer tools are showing following following error:
[Extension Host] rejected promise not handled within 1 second: Error: Failed to start debug session!
[Extension Host] stack trace: Error: Failed to start debug session!
at LaunchResolver.<anonymous> (/home/ravi/.vscode/extensions/ms-iot.vscode-ros-0.8.4/out/src/debugger/configuration/resolvers/ros1/launch.js:310:32)
at Generator.next (<anonymous>)
at fulfilled (/home/ravi/.vscode/extensions/ms-iot.vscode-ros-0.8.4/out/src/debugger/configuration/resolvers/ros1/launch.js:7:58)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
Please see a screenshot below:
Related
Setup :
#angular/cli#8.1.2
#ionic/cli#6.12.3
cordova#10.0.0
npm#6.14.10
“protractor”: “~5.4.0
Mac OS : Catalina
This is the error I am getting
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
:information_source: ｢wdm｣: Compiled successfully.
[12:08:58] I/launcher - Running 1 instances of WebDriver
[12:08:58] I/direct - Using ChromeDriver directly...
[12:08:58] E/runner - Unable to start a WebDriver session.
[12:08:58] E/launcher - Error: Error: spawn Unknown system error -86
at ChildProcess.spawn (internal/child_process.js:403:11)
at Object.spawn (child_process.js:553:9)
at exec (/Users/sunilharan/Documents/Projects/IONIC/App_NAME/node_modules/selenium-webdriver/io/exec.js:116:27)
at /Users/sunilharan/Documents/Projects/IONIC/App_NAME/node_modules/selenium-webdriver/remote/index.js:219:25
at processTicksAndRejections (internal/process/task_queues.js:93:5)
[12:08:58] E/launcher - Process exited with error code 100
This same setup is working on another machine running on M1 chip. I have tried on different computers but not working on any of them except my M1 Macbook Pro.
This is an issue with the latest chromedriver on MacOS. Please see detailed resolutions in this ticket.
"As a general solution, simply avoid using the chromedriver that has _m1 in its filename if you are on an Intel mac."
OSX fix Selenium Chromedriver launch error spawn Unknown system error -86 Bad CPU type in executable?
Given:
machine connected through VPN (SitePoint) to company private network
vscode runs with the proxy pac configuration switch --proxy-pac-url=http://<myhostname>/<path_to_proxypac>/proxy.pac":
any extensions can be seen and installed successfully
python 3 project opened with vscode
development container configuration files... (Python 3) added to project
Add the following extensions to .devcontainer.json
"extensions": [
"ms-python.python",
"himanoa.python-autopep8",
"wholroyd.jinja",
"magicstack.MagicPython",
]
Reopened project in container
Expected:
extensions configured in .devcontainer.json are successfully installed in the Dev Container mode vs code.
Actual:
the list of DEV CONTAINER: PYTHON 3 - INSTALLED is empty
and got the following error in vs code terminal
[27528 ms] Installing extensions...
[27528 ms] getaddrinfo ENOTFOUND marketplace.visualstudio.com
getaddrinfo ENOTFOUND marketplace.visualstudio.com
getaddrinfo ENOTFOUND marketplace.visualstudio.com
getaddrinfo ENOTFOUND marketplace.visualstudio.com
[27528 ms] Exit code 1
Mentions:
1. I can install extensions from Dev Container mode vs code.
What am I supposed to do to address this problem?
Could this be an issue or feature request for Remote-Containers extension?
Try it:
In Visual Studio Code, go to:
File > Preferences > Settings
Then click on tab User > Application > Proxy
Enter your proxy address in the field, as an example:
http://proxy_userid:proxy_password#proxy_ip:proxy_port
If your password contains special characters, replace it with the URL Encode value. See here: http://www.cjdinfo.com.br/utilitario-tabela-caracteres
Or try it:
https://code.visualstudio.com/docs/setup/network
Appium Server version: 1.7.1
OS: Windows 8
While running the code I got
org.openqa.selenium.WebDriverException:
An unknown server-side error occurred while processing the command.
Original error:
Error executing adbExec.
Original error:
'Command 'D\:\\Android\\android-sdk\\platform-tools\\adb.exe -P 8080 -s ------ install C\:\\Users\\resi\\AppData\\Local\\Programs\\appium-desktop\\resources\\app\\node_modules\\appium\\node_modules\\appium-unlock \\bin\\unlock_apk-debug.apk' exited with code 1';
Stderr: 'Failed to install C:\Users\resi\AppData\Local\Programs\appium-desktop \resources\app\node_modules\appium\node_modules\appium-unlock\bin\unlock_apk-debug.apk:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE:
Package io.appium.unlock signatures do not match the previously installed version; ignoring!]'; Code: '1'
error and Appium Setting page is opened and instant closed in real Android device instead of opening app (.apk file)
You need to cleanup the device you are using:
Go to Settings -> Apps
Delete you application under test using Uninstall for all users menu
Delete Appium Settings app
Restart your test and it should work
Ibm mobilefirst development server failed to start showing error
objc[77281]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/bin/java and /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
/Users/test/Documents/sathyarajworkspace/eclipse/plugins/com.worklight.worklight-artifacts_7.1.0.00-20151012-1525/liberty/wlp/bin/server: line 764: 77281 Abort trap: 6 "${JAVA_CMD}" "$#"
Since i lost eclipse version of 6.3 i copied eclipse from another mac.
when i tried to run the development server this error shown.
i have also updated to current version of IBM MF still issue exist.
How to fix this issue in mac.
UPDATE:
killall -9 java
Killing java process worked.Thanks
The port is taken.
Try killing the Java process and then start the server again.
in command prompt, run lsof -i :10080
then kill the ports running with kill -9 <port_number>
in the "server" tab in eclipse, delete the "mobilefirst development server"
close eclipse, reopen eclipse, the server should recreate
start the server again
First post.
Hi, I'm trying to run appium by executing the following command lines from eclipse:
Process pr = rt.exec(new String[] {"/usr/local/bin/node", "/usr/local/bin/appium"});
And then I run an AppiumDriver with the url and it's capabilities (also from eclipse): AppiumDriver ad = new AppiumDriver(new URL(url), this.capabilities);
These errors follow:
[36minfo[39m: [debug] Dynamic bootstrap path:
/Users/philippe.pageau/Library/Application
Support/appium/bootstrap/bootstrap-072528be314c3cc6.js
[36minfo[39m:
[debug] Reusing dynamic bootstrap:
/Users/philippe.pageau/Library/Application
Support/appium/bootstrap/bootstrap-072528be314c3cc6.js
[36minfo[39m:
[debug] Attempting iOS device log capture via libimobiledevice
idevicesyslog
[33mwarn[39m: Could not capture device log using
libimobiledevice idevicesyslog. Libimobiledevice probably isn't
installed
[36minfo[39m: [debug] Attempting iOS device log capture
via deviceconsole
[33mwarn[39m: Could not capture logs from device.
Continuing without capturing logs.
[36minfo[39m: [debug] Creating iDevice object with udid XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[36minfo[39m: [debug] Couldn't find ideviceinstaller, trying
built-in at
/usr/local/lib/node_modules/appium/build/libimobiledevice-macosx/ideviceinstaller
[36minfo[39m: [debug] Cleaning up appium session [36minfo[39m:
[debug] Error: Could not initialize ideviceinstaller; make sure it is
installed and works on your system
at [object Object].IOS.getIDeviceObj (/usr/local/lib/node_modules/appium/lib/devices/ios/ios.js:909:13)
at [object Object].IOS.installToRealDevice (/usr/local/lib/node_modules/appium/lib/devices/ios/ios.js:856:32)
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:607:21
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:246:17
at iterate (/usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:146:13)
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:157:25
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:248:21
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:612:34
at [object Object]. (/usr/local/lib/node_modules/appium/lib/devices/ios/ios.js:1527:14)
at /usr/local/lib/node_modules/appium/node_modules/underscore/underscore.js:890:21
at [object Object]._onTimeout (/usr/local/lib/node_modules/appium/lib/devices/ios/ios-log.js:166:7)
at Timer.listOnTimeout (timers.js:110:15)
[36minfo[39m: [debug] Responding to client with error: {"status":33,"value":{"message":"A
new session could not be created. (Original error: Could not
initialize ideviceinstaller; make sure it is installed and works on
your system)","origValue":"Could not initialize ideviceinstaller; make
sure it is installed and works on your system"},"sessionId":null}
[36minfo[39m: [37m<-- POST /wd/hub/session [39m[31m500[39m[90m
11133.802 ms - 300[39m [90m[39m
Exception in thread "main" org.openqa.selenium.SessionNotCreatedException: A new session could
not be created. (Original error: Could not initialize
ideviceinstaller; make sure it is installed and works on your system)
(WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 11.35 seconds
The errors show that it didn't find ideviceinstaller nor libimobiledevice (which I both installed)
I followed these instructions
Appium throws "ideviceinstaller" not found when launched through Eclipse - Java
http://technotesonthego.blogspot.ca/2013/10/install-libimobiledevice-on-mac-os-x.html
Note that I wish to execute everything from eclipse, allowing the QA to not worry about those things. It works with the GUI (I uninstalled it afterwards) and it also works when I run appium in the terminal and execute AppiumDriver ad = new AppiumDriver(new URL(url), this.capabilities); with eclipse.
I did my research, and asking the question to stackoverflow is my last resort.
Did I miss something?
EDIT
Also, I tried executing /usr/local/lib/node_modules/appium/build/libimobiledevice-macosx/ideviceinstaller and it gave me this error : dyld: Library not loaded: #executable_path/../lib/libimobiledevice.3.dylib Referenced from: /usr/local/lib/node_modules/appium/build/libimobiledevice-macosx/ideviceinstaller Reason: image not found Trace/BPT trap: 5
Tried on Appium 1.4.8:
Step 1: install the "brew" command
Step 2: run the following command: brew install --HEAD ideviceinstaller
Step 3 (optional): click Appium/Reset Preferences and then close & open Appium
Good luck.