Robotics Systems Commons: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732015-12-10T14:32:41ZOpen Source Collaboration Platform
Redmine Bug #2472 (In Progress): Under windows rsc::misc timestamps are in milliseconds.https://code.cor-lab.de/issues/24722015-12-10T14:32:41ZM. Goerlichmgoerlic@techfak.uni-bielefeld.de
<p>under windows the send timestamp of the spread transport seems to be in milliseconds.</p>
<p>As Jan already found out the problem resides in the rsc::misc function for gathering the current timestamp (sorry, forgot the name...).</p>
<p>Here is a printout of a rsb-loggercpp that shows the data received from the windows host on a linux machine. Note the send timestamp.</p>
<pre>
-------------------------------------------------------------------------------
Event
Scope /kinect2_old/persontracking/state/5/
Id EventId[participantId = UUID[2c098dad-ab20-4e39-8c70-39330fb7a5c4], sequenceNumber = 2]
Type bytearray
Origin 2c098dad-ab20-4e39-8c70-39330fb7a5c4
Timestamps
Create 2015-Dec-10 15:16:13.341861+??:??
Send 2015-Dec-10 15:16:13.341000+??:??
Receive 2015-Dec-10 15:16:13.342695+??:??
Deliver 2015-Dec-10 15:16:13.342696+??:??
Payload (bytearray, length 4)
0x0000 0a 02 08 05
-------------------------------------------------------------------------------
</pre> Bug #1430 (New): Fix debian packaging to conform more strongly to debian policyhttps://code.cor-lab.de/issues/14302013-02-20T07:37:10ZA. Tuleualexandre.tuleu@epfl.ch
<p>I know this is an hassle, but it gives me lot of maintainance nightmare at higher levels because the debian policy is not strongly followed in the debian packaging of librsc.</p>
<p>Please fix the following issues :</p>
<ul>
<li>have a runtime and a dev package.</li>
<li>Make sure runtime package have the same full name than the library (with SONAME). Currently it should be librsc0.9</li>
<li>No header in the runtime package, but in the dev package</li>
<li>No librsc.so in the runtime, but in the dev package a symlink to librsc.so</li>
<li>fixed pkg-config file for this setup (no runtime path, and point simply to -lrsc)</li>
<li>provide a shlibs file for better debian integration. (see section 8.6). Basically it will be used by dpkg to maintain its database of symbols / shared lib dependency</li>
</ul>
<p>This come from the debian manual policy, and could causes problem, especially when using pkg-config to symlink with rsc (which is the case for liboncilla compilation from webots).</p>
<p>Please refer to <a class="external" href="http://www.debian.org/doc/debian-policy/ch-sharedlibs.html">http://www.debian.org/doc/debian-policy/ch-sharedlibs.html</a></p> Bug #1292 (Feedback): Do not set EXTERNAL_INCLUDE_COMMANDS in rsc/rst.pc.in by defaulthttps://code.cor-lab.de/issues/12922012-12-11T10:40:46ZS. Herbrechtsmeiersherbrec@cit-ec.uni-bielefeld.de
<p>The external include commands are not needed by default and are workarounds for external problems. Additionally it doesn't work with the PKG_CONFIG_SYSROOT_DIR option of pkg-config which is useful when cross compiling packages.</p> Bug #746 (New): Logger-Tree in LoggerFactory is not cleaned from abandoned loggers (pruning?)https://code.cor-lab.de/issues/7462011-12-05T18:14:45ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>This map is filled up all the time but abandoned loggers are not removed.</p>
<p>A nice solution with the new LoggerProxy would be to invoke a callback of LoggerFactory in the destructor of the proxy.</p>