diff options
| -rw-r--r-- | ISSUES | 23 |
1 files changed, 23 insertions, 0 deletions
| @@ -44,16 +44,25 @@ Create, modify and execute operation on ballots. | |||
| 44 | * as the ballot tool is not an API, doesn't it make most sense to have | 44 | * as the ballot tool is not an API, doesn't it make most sense to have |
| 45 | voting tests as shellscripts? | 45 | voting tests as shellscripts? |
| 46 | 46 | ||
| 47 | YES. | ||
| 48 | |||
| 47 | * how should FOREVER be handled in config files? | 49 | * how should FOREVER be handled in config files? |
| 48 | 50 | ||
| 51 | There are keywords (NEVER, FOREVER, see util/strings.c). I would probably | ||
| 52 | for now not bother to check if the options are sane (i.e. vote finishes at eternity). | ||
| 53 | |||
| 54 | |||
| 49 | Multiple authorities: | 55 | Multiple authorities: |
| 50 | * what should happen when duplicate vote is detected? where do we "complain"? | 56 | * what should happen when duplicate vote is detected? where do we "complain"? |
| 51 | (can't always detect this on submission, as two auth. might get different votes) | 57 | (can't always detect this on submission, as two auth. might get different votes) |
| 52 | 58 | ||
| 59 | GNUNET_log (WARNING) | ||
| 53 | 60 | ||
| 54 | * When is the threshold crypto set up? Don't we need another | 61 | * When is the threshold crypto set up? Don't we need another |
| 55 | time for when authorities start to set up the shared secret? | 62 | time for when authorities start to set up the shared secret? |
| 56 | 63 | ||
| 64 | True. | ||
| 65 | |||
| 57 | 66 | ||
| 58 | exceptions and static initializers: when moving a class and not running 'gradle msgtypes', | 67 | exceptions and static initializers: when moving a class and not running 'gradle msgtypes', |
| 59 | this nice message pops up: | 68 | this nice message pops up: |
| @@ -69,13 +78,27 @@ java.lang.NoClassDefFoundError: Could not initialize class org.gnunet.construct. | |||
| 69 | 78 | ||
| 70 | Any idea on how to improve the error reporting? | 79 | Any idea on how to improve the error reporting? |
| 71 | 80 | ||
| 81 | Not really. Just don't have those issues in a release ;-). | ||
| 82 | |||
| 83 | |||
| 72 | question on testbed service disconnect adapter: | 84 | question on testbed service disconnect adapter: |
| 73 | * why is this needed? I get the idea, namely that the operation of service connect | 85 | * why is this needed? I get the idea, namely that the operation of service connect |
| 74 | is "canceled" (by calling done) and then the code for disconnecting is called, but why wouldn't | 86 | is "canceled" (by calling done) and then the code for disconnecting is called, but why wouldn't |
| 75 | I want to do this myself? | 87 | I want to do this myself? |
| 76 | 88 | ||
| 77 | 89 | ||
| 90 | For symmetry, and because testbed may want to trigger OTHER operations that | ||
| 91 | were delayed (due to limited resources) until the disconnect was done. | ||
| 92 | |||
| 93 | |||
| 78 | * crypto mismatch is a bit annoying, when will libgcrypt be done? | 94 | * crypto mismatch is a bit annoying, when will libgcrypt be done? |
| 79 | 95 | ||
| 96 | WK and I talked yesterday. He said this weekend, or earlier. There were some | ||
| 97 | additional minor design issues to be discussed first... | ||
| 98 | |||
| 99 | |||
| 80 | consensus+testbed test looks *horrible*, do you have any suggestions on how to improve? | 100 | consensus+testbed test looks *horrible*, do you have any suggestions on how to improve? |
| 81 | 101 | ||
| 102 | If you have a consensus command-line tool, you can try shell scripting | ||
| 103 | instead (and use gnunet-testbed-profiler to start multiple peers from | ||
| 104 | the shell). | ||