Skip to content

Addition of timeout feature? #9

@jayjlawrence

Description

@jayjlawrence

Has any thought been given to a timeout feature? The thinking here is that if the spawned command is spinning we'll want to abort it after a period of time. This leads to increased issue resiliency in the gem user's code.

Posix::Spawn has implemented their own approach to timeout in the gem which (I expect) avoids the safety issues in MRI Ruby's timeout. I did not see how the timeout parameter is passed through to Posix::Spawn in Terrapin. Additionally the other mechanisms for running the command do not appear to have any timeout handling code. Jruby would be addressed as well.

Would this be a welcome addition to the gem?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions