vdemo: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732019-05-22T16:41:38ZOpen Source Collaboration Platform
Redmine Enhancement #2784 (New): check status with other modality than colorhttps://code.cor-lab.de/issues/27842019-05-22T16:41:38ZG. Walckgwalck@techfak.uni-bielefeld.de
<p>Would it be possible to either change the color scheme (configurable), or add another modality to signal success or fail to help color-blind people see quickly the status.<br />What about changing the "check" label to a bold font for errors (pink and red), and maybe italic or underlined for other modes ?</p> Bug #2778 (New): vdemo perturbed by bashrc print-outshttps://code.cor-lab.de/issues/27782018-10-22T08:46:53ZG. Walckgwalck@techfak.uni-bielefeld.de
<p>Seems like an<br /><pre>
echo "Hello World"
</pre><br />in the bashrc, perturbs vdemo start, it won't recognize the screen has started</p>
<pre>
gwalck@brutus:~$ vdemo_sfb.sh
resetting machine names to localhost
-- [2018-10-22T10:41:32] my process id: 8206, vdemo-id: vdemo-sfb-k0U5Bl5dgX
created spread config: /tmp/vdemo-sfb-k0U5Bl5dgX-spread.conf
connecting to localhost: ....error: 'Hello Worldconnected'
</pre>
<p>obvious solution is to remove this echo, but people might have some other bashrc "outputs"</p>
<p>is it something easy to fix at vdemo side ? No necessity nor urgency though</p> Feature #2377 (New): Selectable success modehttps://code.cor-lab.de/issues/23772015-08-31T13:23:11ZG. Walckgwalck@techfak.uni-bielefeld.de
<p>We discovered a use case when a component would start, and successfully finish and the check would be successful. This is currently displayed orange. We are fine with that but with the new code this would result in a start failure and not continuing to load other components.</p>
<p>We would like to have the possibility to choose if successful is on both component to run + check ok (green), or only check ok (orange).</p>
<p>A typical use case is a roslaunch that uploads parameters on the ROS parameter server and finishes nicely. Those parameters are used by a non roslaunched node so cannot be included in the same launch file.<br />Another case is a controller_manager start controller or a rosservice call from bash.</p>
<p>A workaround until this feature is accepted and implemented is to add a blocking function (we added a read) after the successful returning command.</p>