Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732015-02-24T10:43:19ZOpen Source Collaboration Platform
Redmine 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> Bug #2167 (New): Check that RemoteServer instances delete EventId instances in case of RPC timeoutshttps://code.cor-lab.de/issues/21672015-02-04T16:08:22ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>I have observed that EventId instances are collected in a java process in case frequent RPC calls time out. This might be due to the association of responses with requests.</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> Bug #1914 (New): Reader does not work with multi-connector setuphttps://code.cor-lab.de/issues/19142014-07-04T11:44:13ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Originally reported from Timo Korthals on the mailing list:</p>
<blockquote>
<p>wie gestern angekündigt, will ich nun ein seltsames Verhalten des<br />"readers" mitteilen:<br />Situation:<br />1x Informer<br />1x Reader</p>
<p>Wenn der Reader sowohl auf inprocess, als auch auf socket hört, empfängt<br />er keine socket-Nachrichten vom Informer. rsb.conf:<br />[transport.inprocess]<br />enabled = 1<br />[transport.socket]<br />enabled = 1<br />host = localhost<br />server = auto<br />port = 55555</p>
<p>Wenn der Reader nur auf socket hört, dann empfängt er auch Nachrichten<br />vom Informer. rsb.conf:<br />[transport.inprocess]<br />enabled = 0<br />[transport.socket]<br />enabled = 1<br />host = localhost<br />server = auto<br />port = 55555</p>
</blockquote> Bug #1806 (Rejected): RSB-Java Master fails --> Unit Tests, hard-coded hostname? And Maven Errorshttps://code.cor-lab.de/issues/18062014-03-17T10:48:49ZF. Lierflier@techfak.uni-bielefeld.de
<p>Error log:</p>
<pre>
Tests in error:
deactivate(rsb.patterns.ServerTest): Could not create spread connection host=boron, port=4910
activate(rsb.patterns.ServerTest): Could not create spread connection host=boron, port=4910
startServer(rsb.patterns.ServerTest): Could not create spread connection host=boron, port=4910
blocking(rsb.patterns.ServerTest): Could not create spread connection host=boron, port=4910
addMethod(rsb.patterns.RemoteServerTest): Could not create spread connection host=boron, port=4910
INFO: Shutting down due to request and closed socket.
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.103 sec
Running rsb.patterns.ServerTest
Mar 17, 2014 11:44:25 AM rsb.transport.spread.SpreadWrapper makeConnection
INFO: reoccuring SpreadException during connect to daemon: Socket(): java.net.NoRouteToHostException: No route to host
Mar 17, 2014 11:44:28 AM rsb.transport.spread.SpreadWrapper makeConnection
INFO: reoccuring SpreadException during connect to daemon: Socket(): java.net.NoRouteToHostException: No route to host
Mar 17, 2014 11:44:31 AM rsb.transport.spread.SpreadWrapper makeConnection
INFO: reoccuring SpreadException during connect to daemon: Socket(): java.net.NoRouteToHostException: No route to host
Mar 17, 2014 11:44:34 AM rsb.transport.spread.SpreadWrapper makeConnection
INFO: reoccuring SpreadException during connect to daemon: Socket(): java.net.NoRouteToHostException: No route to host
Tests run: 7, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 12.009 sec <<< FAILURE!
Running rsb.patterns.DataCallbackTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running rsb.patterns.RemoteServerTest
Mar 17, 2014 11:44:37 AM rsb.transport.spread.SpreadWrapper makeConnection
INFO: reoccuring SpreadException during connect to daemon: Socket(): java.net.NoRouteToHostException: No route to host
Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.987 sec <<< FAILURE!
Maven:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 36.687s
[INFO] Finished at: Mon Mar 17 11:44:37 CET 2014
[INFO] Final Memory: 24M/286M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on project rsb: There are test failures.
[ERROR]
[ERROR] Please refer to /media/FSM-Lab/lsp-csra-src/generator/jobs/rsb-java-master-toolkit-nightly/workspace/label/master/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[exec] ==================
Build step 'Invoke top-level Maven targets' marked build as failure
Skipping publisher since build result is FAILURE
Finished: FAILURE
</pre> 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.deBug #1483 (New): Common Lisp logger stumbles upon wrong / unknown config optionshttps://code.cor-lab.de/issues/14832013-05-02T09:31:41ZAnonymous
<p>For the interoperability tool-chain we added the configuration option</p>
<pre>
wireschemamapping = "^/icub.*/.*/state$"=rosetta<MechanismBottleDataHolder,yarp.icub.angles.state>;"^/icub.*/.*/rpc$"=rosetta<MechanismBottleDataHolder,yarp,icub.angles.command>;"^/icub.*/cam.*"=rosetta<MechanismBottleDataHolder,yarp.icub.image>;"^/icub.*/
</pre>
<p>This is not known to the cl tools yet, so it complains (see error below). It should maybe just warn about unknown syntax, or provide an option to continue on errors.</p>
<p>The error:</p>
<pre>
rsb-logger --style=monitor socket:/
unhandled SIMPLE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING
{1007680E63}>:
Syntax error in line 30, contents
"wireschemamapping = \"^/icub.*/.*/state$\"=rosetta<MechanismBottleDataHolder,yarp.icub.angles.state>;\"^/icub.*/.*/rpc$\"=rosetta<MechanismBottleDataHolder,yarp,icub.angles.command>;\"^/icub.*/cam.*\"=rosetta<MechanismBottleDataHolder,yarp.icub.image>;\"^/icub.*/texture/.*\"=rosetta<MechanismBottleDataHolder,yarp.icub.image>".
0: (SB-DEBUG::MAP-BACKTRACE
#<CLOSURE (LAMBDA # :IN BACKTRACE) {1007D7F86B}>
:START
0
:COUNT
128)
1: (BACKTRACE 128 #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {1000206593}>)
2: (SB-DEBUG::DEBUGGER-DISABLED-HOOK
#<SIMPLE-ERROR "~@<Syntax error in line ~D, contents ~S.~@:>" {1007D7C973}>
#<unavailable argument>)
3: (SB-DEBUG::RUN-HOOK
*INVOKE-DEBUGGER-HOOK*
#<SIMPLE-ERROR "~@<Syntax error in line ~D, contents ~S.~@:>" {1007D7C973}>)
4: (INVOKE-DEBUGGER
#<SIMPLE-ERROR "~@<Syntax error in line ~D, contents ~S.~@:>" {1007D7C973}>)
5: (ERROR
"~@<Syntax error in line ~D, contents ~S.~@:>"
30
"wireschemamapping = \"^/icub.*/.*/state$\"=rosetta<MechanismBottleDataHolder,yarp.icub.angles.state>;\"^/icub.*/.*/rpc$\"=rosetta<MechanismBottleDataHolder,yarp,icub.angles.command>;\"^/icub.*/cam.*\"=rosetta<MechanismBottleDataHolder,yarp.icub.image>;\"^/icub.*/texture/.*\"=rosetta<MechanismBottleDataHolder,yarp.icub.image>")
6: (RSB:OPTIONS-FROM-STREAM
#<SB-SYS:FD-STREAM for "file /home/norro/.config/rsb.conf" {1007D737A3}>)
7: (RSB:OPTIONS-FROM-DEFAULT-SOURCES :CONFIG-FILES NIL)
8: (RSB.TOOLS.LOGGER:MAIN)
9: ((FLET #:WITHOUT-INTERRUPTS-BODY-54 :IN SAVE-LISP-AND-DIE))
10: ((LABELS SB-IMPL::RESTART-LISP :IN SAVE-LISP-AND-DIE))
unhandled condition in --disable-debugger mode, quitting
</pre> Bug #1401 (New): Sphinx-based documentation for rsb-matlabhttps://code.cor-lab.de/issues/14012013-02-06T19:34:50ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>We need to udpate and transform the rsb-matlab documentation from the Wiki to a Sphinx module.</p> Bug #688 (Feedback): Name resolution does not work with absolute package nameshttps://code.cor-lab.de/issues/6882011-10-31T14:54:49ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>for the logger, a proto file with rsb.protocol.Notification as a member type declaration cannot be resolved. Starting with a dot, this works.</p> Feature #471 (New): Support for RPC clients which do not require a running server parthttps://code.cor-lab.de/issues/4712011-08-04T15:17:20ZL. Schillingmannlschilli@techfak.uni-bielefeld.de
<p>It should be simple to code a rpc client which is able to handle different states of the rpc server availability:</p>
<ul>
<li>reconnect if server disappears and reappears</li>
<li>detect server availability</li>
<li>wait for server to appear (with timeout)</li>
</ul> Bug #390 (New): Handling of sendTime in Informerhttps://code.cor-lab.de/issues/3902011-06-23T19:27:18ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>An <code>Informer</code> returns an <code>Event</code> to the caller after sending it. This is especially useful if the event is created in the informer on behalf of the calling client. Currently, returned events have their <code>sendTime</code> timestamp set in some way. However, it is not quite clear, how this timestamp should be set. There are (at least) the following possibilities:</p>
<ul>
<li>The informer sets the timestamp before passing the event to connectors for sending</li>
<li>Each connector somehow locks the event and sets the timestamp. The least recent connector "wins" </li>
<li>The connector sets the timestamp only if there is just one connector</li>
<li>The informer sets the timestamp after the event has been processed by all connectors</li>
</ul>
<p>After this has been decided, update</p>
<ul>
<li>UML sequence diagrams</li>
<li><a href="https://code.cor-lab.de/projects/rsb/wiki/EventProcessing" class="wiki-page">EventProcessing</a></li>
<li>Implementations</li>
</ul> Feature #340 (Feedback): Implement Distributed Namingservicehttps://code.cor-lab.de/issues/3402011-05-30T09:51:10ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>For introspection in an RSB system comprised by multiple transports, a nameservice implementation is needed.</p>
<p>In contrast to ROS, YARP, XCF, a distributed nameservice is required.</p>
<p>Implementation could be based on:</p>
<ul>
<li>UPNP (btw: could enable DLNA-based use cases...)</li>
<li>Multicast-DNS (check compatibity)</li>
<li>ROS Master (at least evaluate it?)</li>
</ul>
<p>Check relation to model-layer.</p>