Activity
From 05/02/2013 to 05/31/2013
05/31/2013
- 01:47 PM Tasks #1167 (In Progress): Provide Spread transport as plugin (C++)
- 01:45 PM Feature #1521 (Resolved): LocalServer lacks a Callback<void,void> specialization
- 01:45 PM Feature #1521 (In Progress): LocalServer lacks a Callback<void,void> specialization
- An example can be found in the @examples/server@ directory.
- 01:45 PM Feature #1521 (Resolved): LocalServer lacks a Callback<void,void> specialization
- Applied in changeset rsb-cpp|commit:2eefc46c2880bea316bb9e6711d47173514a7bec.
- 12:40 PM Feature #1521 (In Progress): LocalServer lacks a Callback<void,void> specialization
- 01:11 PM RSBag Feature #1481 (In Progress): Support changing timestamp used for indexing in bag-transform
- @bag-merge@ already has the @--transform-timestamp@ option. I have to investigate whether anything needs to be done.
05/30/2013
- 10:04 AM Feature #1521: LocalServer lacks a Callback<void,void> specialization
- I already did this once but it did not quite work for some reason I can't remember. I will try again.
05/29/2013
- 04:00 PM Bug #1497 (Resolved): Receive and Deliver-Timestamps not set correctly
- Looks correct to me now.
- 02:06 AM Bug #1497 (Feedback): Receive and Deliver-Timestamps not set correctly
- @Johannes: Please check whether these changes fix the problem for you.
- 02:51 PM Feature #1521 (Resolved): LocalServer lacks a Callback<void,void> specialization
- Currently it is not possible to register a method with no argument and no return value to a rsb server.
Solution: ...
05/28/2013
- 12:10 AM Bug #1497 (In Progress): Receive and Deliver-Timestamps not set correctly
- 03:27 PM Bug #1519 (Resolved): Option for controlling TCP_NODELAY has wrong name in CL implementation
- Applied in changeset rsb-cl|commit:dcdd182c41b757b0c845ebf3744ebbac97454732.
- 01:18 PM Bug #1519 (Resolved): Option for controlling TCP_NODELAY has wrong name in CL implementation
- The option is called @nodelay@ instead of @tcpnodelay@.
- 03:08 PM Bug #1408 (Resolved): Converter registration should be possible without rewriting default partici...
- Applied in changeset rsb-python|commit:8ec3b1e64674144c7f1165338d82ce35dbf6d447.
- 11:23 AM Bug #1408: Converter registration should be possible without rewriting default participant config...
- I have pushed respective changes to the implementation and the manual. Can someone please review them and verify the ...
- 01:40 PM Bug #1517 (Resolved): TCPNODELAY is off by default in C++
- Applied in changeset rsb-cpp|commit:7672063f86aada6f1056c05599803bd11e30e37f.
- 11:35 AM Bug #1517: TCPNODELAY is off by default in C++
- I think so as well. I just didn't get to it yesterday.
- 11:34 AM Bug #1517 (Resolved): TCPNODELAY is off by default in C++
- TCPNODELAY is off by default in C++, although it should be on, right?
- 01:04 PM Bug #1518 (Resolved): RSB_TRANSPORT_SOCKET_NODELAY documentation seems erroneous
- Applied in changeset rsb-manual|commit:c0f78250c62c74c96a7271043b0b617760af65b6.
- 12:47 PM Bug #1518: RSB_TRANSPORT_SOCKET_NODELAY documentation seems erroneous
- Forgot to paste the link:
http://docs.cor-lab.org/rsb-manual/trunk/html/common.html - 11:51 AM Bug #1518 (Resolved): RSB_TRANSPORT_SOCKET_NODELAY documentation seems erroneous
- In the RSB manual, @tcp_nodelay@ for the socket transport is documented to be set through the environment variable @R...
- 11:31 AM Feature #1149: Allow checking if handlers are registered in Listener
- Martin, Robert, are you planing on implementing the proposed changes or should we do this?
05/27/2013
- 09:40 PM Bug #1408 (In Progress): Converter registration should be possible without rewriting default part...
- 06:31 PM Enhancement #1516 (New): Separate Converter selection strategies for sending and receiving
- Both directions differ significantly. This was already the reason why the connector infrastructure is split into two ...
- 06:29 PM Enhancement #1515 (New): Add data type to all participants, especially listeners
- This would automatically allows to select the correct converter for deserialization. Also, right now the situation is...
- 06:26 PM Bug #1489: Selection of new fundamental converters breaks existing programs
- * For python this means: only register the converters for these types
* For C++: Clients are obliged to use these cl... - 06:21 PM Bug #1489: Selection of new fundamental converters breaks existing programs
- Verdict: We want the same defaults for all languages. This means there is one int and one float type that is consiste...
- 05:21 PM Bug #1497: Receive and Deliver-Timestamps not set correctly
- Generally the problem does not exist in the core but is merely a display problem of the cl logger. What happens is th...
- 04:55 PM Bug #1230 (Closed): Unintuitive error message upon misconfiguration
- The current behavior is OK in all cases Johannes and I could test on MacOS and Linux (But we can still document this,...
- 04:55 PM Tasks #1513 (Resolved): Document exception handling in main function of RSB-using C++ programs
- Each RSB client program should handle exceptions at least in its main method because on certain OSes the exception ty...
- 01:09 PM Tasks #1167: Provide Spread transport as plugin (C++)
- As a separate repository for the single language implementation.
05/22/2013
- 11:27 AM Enhancement #648: Ideas for Recording Data on a Resource-Constrained System
- Do you mean
"a self-contained recording toolchain for resource-constrained systems is still relevant"
or
"a... - 11:22 AM Enhancement #648: Ideas for Recording Data on a Resource-Constrained System
- Yes, it is. Probably not a first priority right now but still relevant.
05/21/2013
- 04:39 PM Feature #759 (Closed): Check RSB Real-Time compatibility
- @Sebastian: please reopen, if you disagree.
- 04:38 PM Feature #759: Check RSB Real-Time compatibility
- Agreed.
- 02:38 PM Feature #759: Check RSB Real-Time compatibility
- Maybe this should be explored in the dedicated rsb-realtime-cpp project?
I am leaning towards closing this and ope... - 02:50 PM Tasks #804 (Closed): Unify Naming of Deployed Executables
- I checked the binaries installed by the RSB and RSBag projects and all follow the scheme...
- 02:43 PM Tasks #892 (Rejected): Apply for GSoC 2012 with RSB Octave Support
- 02:40 PM Enhancement #648: Ideas for Recording Data on a Resource-Constrained System
- Is this still relevant?
If so, we could investigate using the new rsb-realtime-cpp for streaming data for remote r... - 02:35 PM Enhancement #890 (In Progress): Logger should accept multiple URIs
- 01:50 PM Tasks #1448 (Resolved): Test pkg-config
- Applied in changeset rsb-cpp|commit:1981a02fc13ed37731c8240fa443575a59a0d8fe.
05/17/2013
- 07:43 PM Enhancement #1500 (New): Encode version in library name
- If setup in rsc proves to be working, encode rsb version in the library name, which makes parallel installation and p...
05/13/2013
- 11:00 PM Bug #1497 (Resolved): Receive and Deliver-Timestamps not set correctly
- I am not entirely sure which part is causing this, but I am using bag-play to replay old log files and messages from ...
05/10/2013
05/08/2013
- 03:20 PM Feature #1490 (Resolved): Python lacks deserialization support for EventsByScopeMap
- Applied in changeset rsb-python|commit:160600fd72b8dbd2506cbf4490b708706d739b0c.
- 03:00 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- Johannes Wienke wrote:
> Why only 60%? ;)
I did not change change the progress intentionally. Must have been a m... - 02:49 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- Why only 60%? ;) I will merge it back, if that's ok?
- 01:47 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- Looks OK to me.
05/07/2013
- 04:51 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- I have committed serialization support and removed the converter from the default registration. Anything else remaini...
- 03:47 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- Apart from the other things: I don't know how to safely implement serialization because @dict@ is a potentially bad t...
- 03:45 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- Johannes Wienke wrote:
> Jan, I have committed something to a respective feature branch. Do you see any problems wit... - 03:44 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- * I think, we decided to use @"""..."""@ for docstrings
* The @print@ statement should be replaced with proper loggi... - 03:20 PM Feature #1490: Python lacks deserialization support for EventsByScopeMap
- Jan, I have committed something to a respective feature branch. Do you see any problems with this approach?
- 03:15 PM Feature #1490 (Resolved): Python lacks deserialization support for EventsByScopeMap
- There is no converter for this type.
- 01:57 PM Bug #1489 (Resolved): Selection of new fundamental converters breaks existing programs
- The new fundamental converters in python break existing programs as the selection is now different, and e.g. communic...
- 01:55 PM Bug #1408: Converter registration should be possible without rewriting default participant config...
- We should not forget to fix this in 0.9. It's a severe restriction.
- 01:36 PM Bug #1488: Socket transport between cpp and cl mostly fails on mac
- The problem is that the cl logger listens on 127.0.0.1:55555 but cpp first tries to create a server on 0.0.0.0:55555,...
- 11:43 AM Bug #1488: Socket transport between cpp and cl mostly fails on mac
- I have started the logger process with log-level on trace. There is no output when the timesync should connect. If I ...
- 11:39 AM Bug #1488 (Resolved): Socket transport between cpp and cl mostly fails on mac
- I am not sure whether this is a bug of the cl rsb implementation of of the logger, but I observer the following diffe...
05/06/2013
- 07:28 AM RSBag Bug #1421 (In Progress): Verify that string encoding change complies to TIDELog specification
- I discussed this with Ingo and he submitted an updated version. It has not yet been accepted, though.
05/02/2013
- 11:31 AM Bug #1483 (New): Common Lisp logger stumbles upon wrong / unknown config options
- For the interoperability tool-chain we added the configuration option...
Also available in: Atom