View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003389GNUnetcadet servicepublic2014-04-25 13:402018-06-06 22:25
ReporterBart Polot Assigned ToBart Polot Due Date
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product VersionGit master 
Target Version0.11.0pre66Fixed in Version0.11.0pre66 
Summary0003389: Lost message IDs
DescriptionMesh assigns message IDs on queue. This means that cancelled messages still consume IDs, which can break the flow control mechanism.

Mesh should assign the IDs on send or even offer a callback mechanism similar to the public API but for channel-connection.
TagsNo tags attached.

Relationships

has duplicate 0003374 closedBart Polot Mesh reliable tunnels choke after ~500 messages 

Activities

Bart Polot

2014-05-07 17:19

reporter   ~0008306

Fixed in r33180 by assigning the PID on send, not on queue.

Issue History

Date ModifiedUsernameFieldChange
2014-04-25 13:40Bart PolotNew Issue
2014-04-25 13:40Bart PolotStatusnew => assigned
2014-04-25 13:40Bart PolotAssigned To => Bart Polot
2014-04-25 21:36Christian GrothoffPrioritynormal => high
2014-05-07 17:19Bart PolotNote Added: 0008306
2014-05-07 17:19Bart PolotStatusassigned => resolved
2014-05-07 17:19Bart PolotFixed in Version => Git master
2014-05-07 17:19Bart PolotResolutionopen => fixed
2014-05-09 16:34Christian GrothoffCategorymesh service => cadet service
2014-05-15 11:21Bart PolotRelationship addedhas duplicate 0003374
2014-05-15 18:25Christian GrothoffFixed in VersionGit master => 0.11.0pre66
2018-06-06 22:25Christian GrothoffStatusresolved => closed