View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001997 | GNUnet | NSE service | public | 2011-12-08 19:07 | 2011-12-26 22:28 |
| Reporter | Bart Polot | Assigned To | Christian Grothoff | ||
| Priority | high | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.0 | ||||
| Target Version | 0.9.1 | Fixed in Version | 0.9.1 | ||
| Summary | 0001997: Assertion failed in NSE | ||||
| Description | Dez 08 18:58:51-818561 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 0 Dez 08 18:58:51-818707 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 400 Dez 08 18:58:51-818804 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 800 Dez 08 18:58:51-818918 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 1200 Dez 08 18:58:51-819001 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 1600 Dez 08 18:58:51-819096 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 2000 Dez 08 18:58:51-819196 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 2400 Dez 08 18:58:51-819248 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 2800 Dez 08 18:58:51-819311 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 3200 Dez 08 18:58:51-819366 nse-profiler-11818 WARNING nse-profiler: connecting to nse service of peer 3600 Dec 08 19:01:16-404541 nse-20530 ERROR Assertion failed at gnunet-service-nse.c:946. Dec 08 19:01:16-442694 nse-8167 ERROR Assertion failed at gnunet-service-nse.c:946. | ||||
| Tags | No tags attached. | ||||
|
|
Should be fixed in 18705. We were cancelling the transmission of what was possibly the 'previous' round upon receiving data for the 'current' round; but we still remembered not sending the previous round at all (and then asserted on that invariant). Now the code simply sets the flag so that it "forgets" about not sending information from the previous round after receiving information about the current round. While it might be OK (and in some cases slightly better) to still send the information about the previous round, it would seriously complicate our state machine (new state: current round exchanged, previous not!) and that does simply not seem to be worth it. And: we didn't handle this case before either. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-12-08 19:07 | Bart Polot | New Issue | |
| 2011-12-08 19:07 | Bart Polot | Status | new => assigned |
| 2011-12-08 19:07 | Bart Polot | Assigned To | => Bart Polot |
| 2011-12-19 14:27 | Christian Grothoff | Priority | normal => high |
| 2011-12-19 22:39 | Christian Grothoff | Note Added: 0005147 | |
| 2011-12-19 22:39 | Christian Grothoff | Status | assigned => resolved |
| 2011-12-19 22:39 | Christian Grothoff | Fixed in Version | => 0.9.1 |
| 2011-12-19 22:39 | Christian Grothoff | Resolution | open => fixed |
| 2011-12-19 22:39 | Christian Grothoff | Assigned To | Bart Polot => Christian Grothoff |
| 2011-12-26 22:28 | Christian Grothoff | Status | resolved => closed |
