Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732016-08-18T11:17:59ZOpen Source Collaboration Platform
Redmine 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 #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 #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 #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 #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> Feature #1767 (Feedback): Export default plugin folderhttps://code.cor-lab.de/issues/17672014-02-13T16:38:09ZAnonymous
<p>There is some kind of <em>default plugin folder</em> (currently <code>lib/rsbx.x/plugins</code>), where several downstream projects install their plugins (e.g. rst converters, rsb-spread, ...) for convenience. Up to now the downstream projects construct this path by hand.</p>
<p>I suggest that we export e.g. a <code>RSB_DEFAULT_PLUGIN_PATH</code> via cmake config for downstream projects to use. Does that make sense?</p> Feature #1747 (New): Implement introspection event receiver and client APIhttps://code.cor-lab.de/issues/17472014-02-06T17:32:47ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1746 (New): Implement introspection event receiver and client APIhttps://code.cor-lab.de/issues/17462014-02-06T17:32:34ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1745 (New): Implement introspection event receiver and client APIhttps://code.cor-lab.de/issues/17452014-02-06T17:32:22ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1707 (New): Support Java as a client languagehttps://code.cor-lab.de/issues/17072013-12-22T20:19:58ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deFeature #1149 (Feedback): Allow checking if handlers are registered in Listenerhttps://code.cor-lab.de/issues/11492012-08-24T15:00:38ZM. Meiermmeier@techfak.uni-bielefeld.de
<p>For our migration to rsb we need some sort of functionality provided by the <code>rsb::Listener</code> which allows us to check if there are any handlers registered. In earlier version we used the <code>std::set<HandlerPtr></code> in <code>rsb::Listener::Impl</code> which has been removed recently (<a href="https://code.cor-lab.de/projects/rsb/repository/rsb-cpp/revisions/de636d5533afee40af3b2a2ecee4db6c8325597c" class="changeset" title="Removed unused member variable in src/rsb/Listener.cpp * src/rsb/Listener.cpp: removed unused mem...">rsb-cpp|de636d55</a>). So we would like to have at least some kind of <code>bool hasHandlers()</code> available.</p> Feature #1139 (In Progress): Reference documentation in error reportshttps://code.cor-lab.de/issues/11392012-08-15T14:06:58ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>It would be nice to refer users to suitable documentation when certain errors are encountered.</p>
<p>This has been suggested before (see <a href="https://code.cor-lab.de/issues/967" class="issue tracker-5 status-3 priority-4 priority-default closed" title="Error message for missing transports is uninformative (Resolved)">#967</a>).</p>
<p>There are examples in other middlewares:<br /><pre>
6.210 [ Warning][DeploymentComponent::configureComponents] The protocol with id 3 did not register a fall-back handler for unknown types!
6.210 [ Warning][DeploymentComponent::configureComponents] triggered by: unknown_t which does not have a transport.
6.210 [ ERROR ][DeploymentComponent::configureComponents] Could not create transport stream for port FRIState with transport id 3
6.210 [ ERROR ][DeploymentComponent::configureComponents] No such transport registered. Check your policy.transport settings or add the transport for type /tFriIntfState
</pre></p>
<p>A more generic approach than the above would be attaching references as data structures to exceptions. The information could then be printed in way suiting the situation at hand. Here is an example of such a feature being implemented as a mixin class for exception classes:<br /><pre>
The bounding indices 1 and 2 are bad for a sequence of length 0.
[Condition of type SB-KERNEL:BOUNDING-INDICES-BAD-ERROR]
See also:
Common Lisp Hyperspec, _bounding index designator_ [:glossary]
Common Lisp Hyperspec, _SUBSEQ-OUT-OF-BOUNDS:IS-AN-ERROR_ [:issue]
</pre><br />Where the <code>_..._</code> parts are hyperlinks.</p>
Where could this be used?
<ul>
<li>Incompatible payload type vs. informer type => "polymorphic informer" (<a href="/projects/rsb/repository/rsb-manual/revisions/20f6d6bc/entry/troubleshooting.rst#L215" class="source">source:rsb-manual|troubleshooting.rst@20f6d6bc#L215</a>)</li>
</ul> Feature #729 (New): Allow regex-based converter selection for deserializinghttps://code.cor-lab.de/issues/7292011-11-23T12:26:50ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>e.g. I want the same converter to deserialize all rst-types.</p>
<p>This is required for an improved matlab integration.</p>