Skip to content

Panic in kbucket/table.go was triggered. #141

Closed
@whyrusleeping

Description

@whyrusleeping

The panic on line 71 of table.go was triggered. I left it there as a reminder to myself to eventually handle the extremely rare case of kbucket splitting, and apparently, that case was triggered. Ill need to come up with a fix for it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugA bug in existing code (including security flaws)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions