Activity
From 02/12/2018 to 03/13/2018
03/02/2018
-
10:33 AM Bug #4525 (New): Destructing a ChronoSync socket object shuts down the face
- Currently the ChronoSync socket class accepts a reference to a Face object. I think this is intended to support using...
02/13/2018
-
04:15 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- Two related commits:
- https://gerrit.named-data.net/#/c/4535/
- https://gerrit.named-data.net/#/c/4536/
-
- If we don't, then may be we wouldn't see the error. On testbed, we ARE adding ndnlp headers now.
-
11:25 AM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- If we don't set any tags on the data packet then the lpPacket should be empty and we would be sending a Data packet w...
02/12/2018
-
- Ashlesh Gawande wrote:
> Okay, the user specified limit will replace `MAX_NDN_PACKET_SIZE` while comparing to syncR... -
- The testbed size has grown considerably. Also, having separate chronosync prefixes for NAME and COORDINATE inflated t...
-
- Would it be possible to post the ChronoSync log before the crash from this node and other nodes?
When we used NSync ... -
- Okay, the user specified limit will replace MAX_NDN_PACKET_SIZE while comparing to syncReply size?
-
- The solution is incomplete, as it didn't provision for NDNLPv2 headers, resulting in the following error
```
1518... -
Also available in: Atom