Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732016-11-08T11:19:38ZOpen Source Collaboration Platform
Redmine Feature #2673 (In Progress): In addition to DISPLAY_NAME, the introspection system should accept ...https://code.cor-lab.de/issues/26732016-11-08T11:19:38ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>The introspection system should read an environment <code>DISPLAY_VERSION</code> or similar to populate a "component version" field for the current process.</p>
<p>When looking at processes via introspection, it would often be convenient to know, which version of the underlying program is being executed.</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> Feature #2555 (In Progress): Allow easy debugging of RSB configurationhttps://code.cor-lab.de/issues/25552016-06-05T22:12:33ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>With RSB configuration, it is sometimes hard to debug issues or even understand what is going on exactly.</p>
One way would be an appropriate logging configuration, but not an <em>easy</em> way:
<ul>
<li>Requires knowledge about logger hierarchy (i.e. something like <code>export RSB_RSC_LOGGING_RSC_CONFIG=ALL</code>)</li>
<li>Requires modifying the configuration which may interfere with the issue being debugged</li>
<li>Requires sifting through tons of output and figuring out what is going on</li>
<li>Depends on the RSB implementation</li>
</ul>
A better solution might be
<ul>
<li>Set an environment variable <code>__CONFIG_DEBUG</code> </li>
<li>Process it outside the configuration system (as to not interfere)</li>
<li>The output should be minimal (as to not require searching for the relevant information)</li>
</ul> Feature #2227 (Feedback): Symlinks/Aliases for Scopeshttps://code.cor-lab.de/issues/22272015-04-21T14:24:14ZC. Leichsenringcmertes@cit-ec.uni-bielefeld.de
<p>For various reasons it would be useful to make the same informer have multiple scopes, i.e. de facto symlinks or aliases for scopes. Example use cases would be:</p>
<ul>
<li>provide a list of services or devices by human-readable name and number</li>
<li>list services by different criteria</li>
<li>provide different formats under different scopes but link to a default scope</li>
<li>.... basically every reason why one would want symlinks in file systems, too</li>
</ul> Feature #2185 (New): Provide Contrib Library or Folder for Community Additionshttps://code.cor-lab.de/issues/21852015-02-24T10:43:19ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>The proposal here is to provide a <code>contrib</code> folder or library that contains community additions to the framework core. These additions should primarily consist of plugins or additional implementations for the RSB extension points that do not justify a standalone plugin library or can not (yet) be included in the core library. This should allow faster dissemination of new experimental features to the community without fragmentation or erosion of the library core.</p>
<p>The technical means to achieve this (folder vs. library, cmake components or not, integration with core documentation, ...) needs to be discussed.</p> Feature #2170 (New): Visual indication when rsb-logger* (or any other rsb-tool) is readyhttps://code.cor-lab.de/issues/21702015-02-09T16:58:43ZN. Kösternkoester@techfak.uni-bielefeld.de
<p>When providing/loading multiple idl path(s)/files(s), the logger may take some time to load (as described <a href="http://docs.cor-lab.de//rsb-manual/0.11/html/tool-logger.html#tool-logger" class="external">here</a> and as expected).</p>
<p>Example:</p>
<pre>
rsb-loggercl --idl-path="/vol/csra/releases/trusty/lsp-csra-nightly/share/rst0.11/proto/stable/" \
--idl-path="/vol/csra/releases/trusty/lsp-csra-nightly/share/rst0.11/proto/sandbox/" \
--load-idl="/vol/csra/releases/trusty/lsp-csra-nightly/share/rst0.11/proto/**/*.proto" \
--style=detailed \
/rsbopencv/persons/
</pre>
<p>However, (for usability reasons) it would be nice to get a visual indication/feedback (e.g. simple print saying <strong><code>ready</code></strong>) to know if the logger is ready. This is important when using rsb with socket communication, as the order of launching components is important here.</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> Feature #2051 (In Progress): Qt-based graphical event loggerhttps://code.cor-lab.de/issues/20512014-10-09T09:12:23ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<p>initial commit to feature branch "feature-loggerqt"</p> Feature #1993 (In Progress): Rebuild introspection database when clock jumpshttps://code.cor-lab.de/issues/19932014-09-14T10:58:37ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
When detecting an implausible time difference between previous and current update (this is probably more robust than trying to detect suspend/resume and similar situation explicitly), do the following:
<ul>
<li>Cancel update timer</li>
<li>Flush database (including hosts, which does not normally happen)</li>
<li>Do a full introspection survey to repopulate the database</li>
<li>Reinstall update timer</li>
</ul> Feature #1982 (In Progress): Enable introspection senders by default?https://code.cor-lab.de/issues/19822014-09-05T16:45:47ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>I think we decided to enable introspection by default at some point.</p>
<p>Now we should probably discuss when and how we want to make that transition after the implementations get pushed.</p> Feature #1922 (New): Include environment variables in introspection messages describing processeshttps://code.cor-lab.de/issues/19222014-08-04T10:20:21ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>Probably useful</li>
<li>For parity with commandline options</li>
</ul> Feature #1870 (New): Allow (optional) parallel method callshttps://code.cor-lab.de/issues/18702014-05-08T12:36:06ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>Johannes will commit patches containing a short-term workaround for C++ and Java</li>
</ul> Feature #1839 (In Progress): Reference documentation in conditionshttps://code.cor-lab.de/issues/18392014-04-13T16:00:56ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1825 (New): bag record: Start timestamp for remote recording starthttps://code.cor-lab.de/issues/18252014-03-31T21:03:35ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul>
<li>The start method of the remote control interface should accept an optional timestamp</li>
<li>When such a timestamp is supplied, the method will block until the specified time</li>
<li>Recording will start and the method will return</li>
</ul>