Skip to content

Implement hard timeout #35

@thesamesam

Description

@thesamesam

Unfortunately, a098d83 (#26) appears insufficient. I've observed this a bunch of times and poked a tiny bit more yesterday. Users hit it when our sks instances on infra freeze up, etc.

It appears that gpg doesn't commit to having the timeout work in all cases, see https://dev.gnupg.org/T3893:

However if the server stops or some ugly proxy sending in the middle of a transaction we have no real way to set timeout; there are just too many ways a connection can be slowed down.

Accordingly, I think we need a hard timeout from the Python side when invoking gpg.

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