-
Notifications
You must be signed in to change notification settings - Fork 5
Detect routing loops #112
Copy link
Copy link
Open
Labels
a:kannaderArea: in the kannader-* cratesArea: in the kannader-* cratesc:mediumComplexity: mediumComplexity: mediumn:devNeeds: development workNeeds: development workp:highPrio: mediumPrio: mediumt:bugType: bugType: bug
Milestone
Metadata
Metadata
Assignees
Labels
a:kannaderArea: in the kannader-* cratesArea: in the kannader-* cratesc:mediumComplexity: mediumComplexity: mediumn:devNeeds: development workNeeds: development workp:highPrio: mediumPrio: mediumt:bugType: bugType: bug
This should probably be done after #111, as we're also interested in routing loops that have only us as a server (though this might be useful even without #111, as it allows detecting routing loops where there's at least one other well-behaved server)