Skip to content

PriorityQueue for dead Connection can have the same timestamp #936

@paulefoe

Description

@paulefoe

I recently started investigating this issue in aioelasticsearch:
aio-libs/aioelasticsearch#100

And it turns out that potentially if few of the connections getting killed at the same time it could raise an error because PriorityQueue tries to compare two instances of Connection.
In my opinion, two instances of Connection should be considered equal and PriorityQueue then can easily handle such a situation.

I'd gladly provide a PR for that feature if you're okay with this.

Here's what I did in case of aioelasticsearch:
aio-libs/aioelasticsearch#164

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions