Skip to content

Plugin install failure exit codes are not unique #15295

@w33ble

Description

@w33ble

I was just debugging a problem in libesvm where installations failed to download, and was using the exit code (74) to handle that case.

This was fine until I ran it several times and the plugin was already installed, since that exit code was the same (74).

This meant that I needed to write a workaround to parse stdout, which isn't ideal. It would be great if these (and perhaps other) errors used different exit codes so that scripts that consume the plugin tool could more easily react differently based on the reason for failure.

Metadata

Metadata

Assignees

No one assigned

    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