Skip to content

Make brew-cask commands resilient to problems with a single Cask #179

Closed
@phinze

Description

We see issues like #178 on the regular, and their impact could be greatly reduced with a little bit of defensive coding around cask loading.

Problems with one cask shouldn't bring down the entire brew-cask universe.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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