Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732016-05-10T12:48:26ZOpen Source Collaboration Platform
Redmine Enhancement #2545 (Resolved): Avoid double converter registration warning.https://code.cor-lab.de/issues/25452016-05-10T12:48:26ZM. Pohlingmpohling@cit-ec.uni-bielefeld.de
<p>Please remove this annoying message during converter registration:</p>
<pre>WARNING: Converter with signature ConverterSignature [schema=.rct.FrameTransform, datatype=class rct.Transform] already registered in DefaultConverterRepository. Existing entry will be overwritten!</pre>
<p>Because there is no method to check if a converter was already registered by other components within the same vm there is no way to avoid this message without centralized converter loading.</p> Enhancement #2403 (Resolved): Remove implementation-dependant printed representation of objects f...https://code.cor-lab.de/issues/24032015-09-30T08:37:00ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deEnhancement #2371 (Resolved): Introspection receiver should only extend, never reduce informationhttps://code.cor-lab.de/issues/23712015-08-28T11:24:03ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Currently the introspection receiver uses the most recently received value in all cases. For fields like <code>hardware-version</code> and <code>software-version</code> in <code>host-info</code>, this can lead to useful information being deleted when one process sends an introspection event containing the information before a different process send an introspection event lacking the information.</p> Enhancement #2369 (Resolved): Move copied timestamps to namespacehttps://code.cor-lab.de/issues/23692015-08-26T16:17:56ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Attached is a patch which copies timestamps to a namespace prefixed with <code>rsbag:</code> to prevent name clashes. Additionally, receive time is now also copied to be consistent.</p> Enhancement #1026 (Resolved): Add transport class [Common Lisp]https://code.cor-lab.de/issues/10262012-06-25T12:48:57ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
The new <code>Transport</code> class would represent properties of transport as a whole (e.g. Spread, socket, inprocess),
<ul>
<li>Instances should aggregate the respective factory objects (in-push, in-pull, out, etc.)</li>
<li>Some Connector properties such as schema list could be moved into the new <code>Transport</code> class</li>
</ul>