Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732018-10-09T14:34:32ZOpen Source Collaboration Platform
Redmine Enhancement #2772 (New): Uniformed path for System-Config in Windowshttps://code.cor-lab.de/issues/27722018-10-09T14:34:32ZS. Barutsbarut@techfak.uni-bielefeld.de
<p>Currently, the path where the system-wide rsb.conf lies is not specified under windows. (see: <a class="external" href="http://docs.cor-lab.org/rsb-manual/trunk/html/specification-config.html#effective-configuration">http://docs.cor-lab.org/rsb-manual/trunk/html/specification-config.html#effective-configuration</a> ; PREFIX is not clearly defined).</p>
<p>Some proposals would be:</p>
<p>- C:\rsb.conf <br />Straightforward but maybe too messy and not clear enough...</p>
<p>- C:\Users\Public\.config\rsb.conf <br />Would have a <span>userprofile</span>\.config\rsb.conf design, but beeing effective for every user (Public) making it system-wide</p>
<p>It is more or less a proposal derived from:<br /><a class="external" href="https://blogs.msdn.microsoft.com/patricka/2010/03/18/where-should-i-store-my-data-and-configuration-files-if-i-target-multiple-os-versions/">https://blogs.msdn.microsoft.com/patricka/2010/03/18/where-should-i-store-my-data-and-configuration-files-if-i-target-multiple-os-versions/</a></p>
<p>Actually "C:\Users\Public" is only intended for documents but with the ".config" subdirectory it should be a nice and clear like in the home directory.</p> Feature #2648 (New): Setters for TimesyncStrategy optionshttps://code.cor-lab.de/issues/26482016-08-18T11:17:59ZM. Goerlichmgoerlic@techfak.uni-bielefeld.de
<p>Currently the strategies can only be configured through boost::po::variables_map s. Filling those by hand is clumsy, direct setters for time frames and buffer sizes at the time frame strategy as well as for the queue size for the approx time strategy would make usage of timesync as library a lot easier.</p> Tasks #2529 (New): Wait for confirmation when joining Spread groups [Python]https://code.cor-lab.de/issues/25292016-04-15T09:28:57ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deTasks #2433 (New): Wait for confirmation when joining Spread groups [C++]https://code.cor-lab.de/issues/24332015-11-16T12:26:33ZJ. Wienkejwienke@techfak.uni-bielefeld.deTasks #2233 (In Progress): Wait for confirmation when joining Spread groupshttps://code.cor-lab.de/issues/22332015-04-23T15:44:40ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>When joining a Spread group, the operation cannot be assumed to have completed before the corresponding membership message has been received from the Spread daemon. As a consequence, events that a certain Spread connection must receive, cannot be sent before the connection in question received its membership message.</p>
<p>When this reasoning and our experimental implementation of a suitable waiting logic appear sound, we have to implement that logic for all languages (and create sub-issues).</p> Enhancement #2225 (New): Use sphinx.ext.ifconfig for version-dependent information in the manualhttps://code.cor-lab.de/issues/22252015-04-20T13:18:39ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>We have several TODOs in the manuals which need to be updated on each release because of things diverging between release and master version. The <code>sphinx.ext.ifconfig</code> module (<a class="external" href="http://sphinx-doc.org/ext/ifconfig.html">http://sphinx-doc.org/ext/ifconfig.html</a>) could help here.</p> Enhancement #2149 (Feedback): Provide simple API to programmatically set preferred convertershttps://code.cor-lab.de/issues/21492015-01-04T06:57:44ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<p>Currently converters can only be configured via the RSC config system. <br />Preferred converters are filtered out in rsb::ParticipantConfig::Transport::handleOption.</p>
<p>As usually the programm needs to specifiy its required converters (rather than the system), there should be an easy mechanism to specify preferred converters on that level.<br />I suggest to add methods addConverter(wireschema, datatype) and addConverters(ConverterNames)</p> Feature #2139 (New): Finalize introspection implementationhttps://code.cor-lab.de/issues/21392014-12-17T14:32:12ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #2138 (New): Allow constructing scopes from a list of component strings (potentially sing...https://code.cor-lab.de/issues/21382014-12-17T13:13:52ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>Java</li>
<li>C++</li>
<li>Python</li>
</ul> Tasks #2137 (New): Handling of missing/not-encodable Hostname and/or HostIdhttps://code.cor-lab.de/issues/21372014-12-17T13:09:51ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Besides implementing this, should be specified in either protocol definition files or specification section of the manual.</p> Tasks #2111 (New): Document converter disambiguation (programmatic and via config file) https://code.cor-lab.de/issues/21112014-11-27T12:30:35ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>Cf. <code>rsbvideoreceiver</code> refactoring branch for an example on how to do this. Location to be decided, maybe troubleshooting.</p> Enhancement #2055 (New): Extend documentation on using and writing converters in the manualhttps://code.cor-lab.de/issues/20552014-10-10T11:56:49ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Robert Haschke wrote:</p>
<blockquote>
<p>Außerdem habe ich ein paar kleine Ergänzungen in der Doku der converters vorgenommen (attached for review). Ich fände es wichtig, dass von der specification-Seite auf die converters-Doku (bislang nur in Form der examples-converters.rst) verwiesen wird. Habe ich aber nicht hinbekommen.</p>
</blockquote>
<p>Robert's patch is attached.</p> Tasks #1901 (New): Documentation should include an example or elaborate more clearly on the seman...https://code.cor-lab.de/issues/19012014-06-24T08:01:53ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>In the <a href="http://docs.cor-lab.de//rsb-manual/trunk/html/examples-basic.html#tutorial-rpc-server" class="external">basic RPC example</a> (in particular for C++), it is only implicitly stated how the template parameters in the LocalServer::Callback class are to be used. It would be better to include at least one example with a signature such as <int, void> to make clear what the roles of two parameters are.</p>
<p>Original reporter: sschulz</p> Enhancement #1831 (Feedback): Provide introspection functionality as shared object (as opposed to...https://code.cor-lab.de/issues/18312014-04-01T14:40:48ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Questions to consider:
<ul>
<li>How should the shared object be exported on the CMake-level?
<ul>
<li>Probably similar to converter plugins in <a href="https://code.cor-lab.de/projects/rst" class="project">Robotics Systems Types</a></li>
<li>However, we probably do not want CMake components since they make everything more complicated</li>
<li>Probably add a <code>RSB_INTROSPECTION_LIBS</code> variable and export it in <code>rsb-config.cmake</code></li>
</ul>
</li>
<li>How should the initialization and cleanup be performed when the introspection shared object is used?</li>
<li>What happens if a client programs links against the introspection shared object and then loads the plugin?</li>
</ul> Feature #1769 (New): Store start and end timestamp of recordinghttps://code.cor-lab.de/issues/17692014-02-14T11:41:13ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>As opposed to timestamps of first/last recorded events.</p>