Activity
From 10/05/2013 to 11/03/2013
10/31/2013
- 11:47 AM Enhancement #1649 (Resolved): If bus is busy cl-logger takes significant time to end
- Confirmed with 0.9 and master.
Using the same setup, logger instantly stops and raises no warning. - 02:38 AM Enhancement #1649 (Feedback): If bus is busy cl-logger takes significant time to end
- Should be fixed in 0.9 and master. Please confirm.
10/29/2013
- 05:24 PM Enhancement #1649 (In Progress): If bus is busy cl-logger takes significant time to end
- 03:28 PM Enhancement #1649 (Resolved): If bus is busy cl-logger takes significant time to end
- If the bus is busy (socket transport, ~100Hz, throughput ~5000), ending the logger takes a significant time (around 5...
10/26/2013
- 11:49 PM Enhancement #1083 (In Progress): Implement communication with congestion control (for reader inte...
- A prototypical implementation can be found in the wip-flow-control branch of the rsb-cl repository.
10/25/2013
- 04:17 AM Bug #1648 (Resolved): error while rsb-loggercl0.10 parses rsb.conf
- Applied in changeset rsb-cl|commit:57da7fd917d757d7c635507b8d8b524879f306ff.
10/24/2013
- 08:16 PM Bug #1648 (In Progress): error while rsb-loggercl0.10 parses rsb.conf
- 08:16 PM Bug #1648: error while rsb-loggercl0.10 parses rsb.conf
- No, it's not a duplicate.
- 08:08 PM Bug #1648: error while rsb-loggercl0.10 parses rsb.conf
- Probably a duplicate of #1483.
- 08:04 PM Bug #1648 (Resolved): error while rsb-loggercl0.10 parses rsb.conf
- The current implementation of rsb-loggercl0.10 seems to have a problem with rsb.config entries:...
10/11/2013
- 06:35 PM Tasks #528 (Closed): Add a "Fixing the Network" Wiki page (also documenting Spread Best Practices)
- I think this is better handled in individual "troubleshooting entries":http://docs.cor-lab.de/rsb-manual/trunk/html/t...
- 06:29 PM RSBag Tasks #1482: Rename bag-merge -> bag-transform
- There is some code but I'm not sure whether this will actually happen. May be subsumed by moving to a single binary w...
- 06:27 PM RSBag Bug #1421 (Closed): Verify that string encoding change complies to TIDELog specification
- I guess, that's all we can do at the moment.
Also available in: Atom