Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FIX: Don't try to generate Gargo.lock on empty workspaces. #3092

Merged
merged 1 commit into from
Sep 14, 2016
Merged

FIX: Don't try to generate Gargo.lock on empty workspaces. #3092

merged 1 commit into from
Sep 14, 2016

Commits on Sep 14, 2016

  1. FIX: Don't try to generate Gargo.lock on empty workspaces. 

    There was a panic! when the command `cargo update` was
executed in a workspace like this:

    mkdir ws
    cd ws
    echo '[workspace]' > Cargo.toml
    cargo new p1
    cargo new p2
    cargo update

The problem is that cargo tries to generate the Cargo.lock file
even if there aren't any members on the workspace.

This fix checks the existence of members in the workspace before trying
to do anything so at least we report an error instead of throwing a
panic!
    @jhbabon
    jhbabon committed Sep 14, 2016
    Configuration menu
    Copy the full SHA
    015e797 View commit details
    Browse the repository at this point in the history