FIX: Don't try to generate Gargo.lock on empty workspaces. #3092
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a
panic!
when the commandcargo update
was executed in a workspace like this: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!
.Issue related #3080