I am running Kubuntu 12.04.4 LTS and ROS Hydro.
When trying to complete the MoveIt! Setup Assistant Tutorial here
http://docs.ros.org/hydro/api/moveit_setup_assistant/html/doc/tutorial.html
everything is working fine until I try Step 4. When I click the "Add Group" button, the MoveIt! Setup Assistant GUI closes and I get the following error:
/opt/ros/hydro/lib/moveit_setup_assistant/moveit_setup_assistant: symbol lookup error: /opt/ros/hydro/lib/libmoveit_setup_assistant_widgets.so: undefined symbol: _ZN3ros7package10getPluginsERKSsS2_RSt6vectorISsSaISsEEb
================================================================================REQUIRED process [moveit_setup_assistant-2] has died!
process has died [pid 14775, exit code 127, cmd /opt/ros/hydro/lib/moveit_setup_assistant/moveit_setup_assistant __name:=moveit_setup_assistant __log:=/home/scratch/.ros/log/a83de36e-06f4-11e4-bcc4-001fd081bf4b/moveit_setup_assistant-2.log].
log file: /home/scratch/.ros/log/a83de36e-06f4-11e4-bcc4-001fd081bf4b/moveit_setup_assistant-2*.log
Initiating shutdown!
================================================================================
[moveit_setup_assistant-2] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
Does anyone know what's going on? Thanks
Related
I am new to electron.js and while making a simple desktop app in electron.js I am getting the following warning.
(node:52973) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15. See https://github.com/electron/electron/issues/28511 for more information. (Use electron --trace-warnings ... to show where the warning was created) libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed [53016:0909/194957.599483:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Operating system:- Ubuntu 20.04
I would like to use the Robot framework to automate a step where the next command is executed in a cmd:
docker-compose logs --no-color --tail=1 the-server
The output of the previous command will be the log of the server named the-server in the docker-compose.yml file.
After I would like to check if the response of this command has the string Started the-server, to check if the server is up.
I'm using the next robot file:
*** Settings ***
Library Process
Library OperatingSystem
Suite Setup log running on ${properties.hostname}
Suite Teardown Terminate All Processes kill=True
Variables C:/Users/TheUser/Desktop/CheckOutRegression/properties.py
*** Test Cases ***
Check if the-server is up
${result} Wait Until Keyword Succeeds 10x 20s Check The-Server
*** Keyword ***
Check The-Server
${resultOfcmd} Run Process docker-compose logs --no-color --tail\=1 the-server shell=yes cwd=${properties.pathToDocker}
Should Contain ${resultOfcmd} 'Started the-server' PASS
Log To Console ${resultOfcmd}
The test-case is always failing with the error:
Keyword 'Check The-Server' failed after retrying 10 times. The last error was: TypeError: 'ExecutionResult' object is not iterable
also I'm not sure if the variable {resultOfcmd} contains the output of the command docker-compose logs --no-color --tail\=1 the-server.
Can anyone help?
Check Process library documentation about Result object from Run Process keyword:
https://robotframework.org/robotframework/latest/libraries/Process.html#Result%20object
You get your results from ${resultOfcmd.stdout}.
You should also use Log To Console before failing keyword to see result before test fails.
Log To Console ${resultOfcmd.stdout} console=yes
after i installed wxWidgets libs and reinstall my version of erlang otp to can i run ":observer.start", my application come fails with this error:
i'm use evm to manage my erlang otp versions.
[info] GET /dashboard/admin
[error] #PID<0.1290.0> running DashboardWeb.Endpoint (cowboy_protocol) terminated
Server: test.lvh.me:5000 (http)
Request: GET /dashboard/admin
** (exit) exited in: :gen_server.call(#PID<0.797.0>, {:checkout, #Reference<0.3971714438.3053715457.259419>, true, 15000}, 5000)
** (EXIT) time out
i researched to try solve error and i finded this link "https://github.com/elixir-ecto/db_connection/issues/127", but i can't solve error, i use elixir 1.6.6 and erlang otp 20.3, i install erlang otp 21.0 like link mention but not work, anyone solved this issue?
I am starting to use Appium Desktop for Mobile Testing.
After the preliminary setup where I set the path and environment variables and defining the desired capabilities, clicking on "Start Session" button result in this message:
"An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: 'Command 'C\:\\Users\\test-PC\\AppData\\Local\\Android\\Sdk\\platform-tools\\adb.exe -P 5037 -s emulator-5554 shell pm list packages com.mol.molwallet' exited with code 1'; Stderr: 'error: closed'; Code: '1'.
Is there any way to find out what causes the "Closure" ? I am using Bluestack as the emulator.
After updating RabbitMQ to version 3.3.3-1 using their APT repository, it will no longer start:
Setting up rabbitmq-server (3.3.3-1) ...
* Starting message broker rabbitmq-server * FAILED - check /var/log/rabbitmq/startup_{log, _err}
[fail]
invoke-rc.d: initscript rabbitmq-server, action "start" failed.
dpkg: error processing package rabbitmq-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
rabbitmq-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
startup_log:
{"init terminating in do_boot",{{case_clause,{ok,[]}},[{rabbit_prelaunch,dist_port_set_check,0,[]},{rabbit_prelaunch,start,0,[]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
startup_err:
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
erl_crash.dump
I'm running Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64)
Erlang version: 1:17.0
I can't seem to find any information on why it is failing to start. Any help would be much appreciated.
Looking at rabbit_prelaunch I think this could happen if you have a config file but it is completely empty. That's not allowed (not a legal Erlang term), but this exception certainly sucks. I'll file a bug to fix that.
EDIT: fixed in 3.3.4.