diff options
-rw-r--r-- | TODO | 33 |
1 files changed, 18 insertions, 15 deletions
@@ -1,19 +1,9 @@ | |||
1 | 0.9.0pre2: | 1 | 0.9.0pre2: |
2 | * CORE: | 2 | * CORE: |
3 | - Jun 27 11:51:54 core-7670 ERROR Assertion failed at gnunet-service-core.c:3616. | 3 | - 2-peer perf test goes WAY over bandwidth limit (i.e. 300 kbps/set, 2 MB/s transfer rate); |
4 | (transport notified us that we connected to ourselves!!!) | 4 | clearly CORE does not properly enforce the limit [MW] |
5 | - transport-level disconnect (i.e. TCP) does not cause core-level | 5 | * Integration test: |
6 | disconnect in a timely fashion (waits for connection timeout); | 6 | - test bootstrapping via hostlist + transport/core/dht connect |
7 | need to figure a way to make it near-instant in those cases | ||
8 | (i.e. rapid reduction in timeout on transport-level disconnect) [CG] | ||
9 | => may have been fixed with instant-notification of disconnect | ||
10 | to core on session-oriented connection hick-up; not perfect but | ||
11 | likely good enough until we get ATS going; still should be tested... | ||
12 | => "peers connected (transport)" now instantly goes to ZERO (core statistic), | ||
13 | but "established sessions" stays up... | ||
14 | - service: | ||
15 | + 2-peer perf test goes WAY over bandwidth limit (i.e. 300 kbps/set, 2 MB/s transfer rate); clearly core does | ||
16 | not properly enforce the limit [MW] | ||
17 | 7 | ||
18 | 0.9.0pre3: | 8 | 0.9.0pre3: |
19 | * Determine RC bugs and fix those (release should have no known real bugs) | 9 | * Determine RC bugs and fix those (release should have no known real bugs) |
@@ -28,9 +18,19 @@ | |||
28 | - needs more testing (especially F2F topology) & transport blacklisting | 18 | - needs more testing (especially F2F topology) & transport blacklisting |
29 | * TRANSPORT-TCP [MW]: | 19 | * TRANSPORT-TCP [MW]: |
30 | - should use hash map to look up sessions | 20 | - should use hash map to look up sessions |
21 | * TRANSPORT: | ||
22 | - [#1585, #1583, #1582] transport-level disconnect (i.e. TCP) does not cause core-level | ||
23 | disconnect in a timely fashion (waits for connection timeout); | ||
24 | need to figure a way to make it near-instant in those cases | ||
25 | (i.e. rapid reduction in timeout on transport-level disconnect) [CG] | ||
26 | => may have been fixed with instant-notification of disconnect | ||
27 | to core on session-oriented connection hick-up; not perfect but | ||
28 | likely good enough until we get ATS going; still should be tested... | ||
29 | => "peers connected (transport)" now instantly goes to ZERO (core statistic), | ||
30 | but "established sessions" stays up... | ||
31 | * NAT/UPNP: [Milan] | 31 | * NAT/UPNP: [Milan] |
32 | - finalize API design | 32 | - finalize API design |
33 | - code clean up | 33 | - [#1609] code clean up |
34 | - testing | 34 | - testing |
35 | - integration with transport service | 35 | - integration with transport service |
36 | - also do UPnP-based (external) IP detection | 36 | - also do UPnP-based (external) IP detection |
@@ -58,6 +58,9 @@ | |||
58 | + search error | 58 | + search error |
59 | + publish error | 59 | + publish error |
60 | + unindex error | 60 | + unindex error |
61 | * CORE: [anyone who can reproduce?] | ||
62 | - Jun 27 11:51:54 core-7670 ERROR Assertion failed at gnunet-service-core.c:3616. | ||
63 | (transport notified us that we connected to ourselves!!!) | ||
61 | * ARM: [CG/Safey] | 64 | * ARM: [CG/Safey] |
62 | - better tracking of which config changes actually need to cause process restarts by ARM. | 65 | - better tracking of which config changes actually need to cause process restarts by ARM. |
63 | - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?) | 66 | - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?) |