FiloSottile/gvt

fetch error message could be more descriptive

Open

#45 opened on May 1, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (67 forks)github user discovery
help wanted

Repository metrics

Stars
 (724 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I made a typo when adding a dependency to vendor/:

 $ gvt fetch golang.org/x/tools/loader
2016/05/01 22:45:32 command "fetch" failed: lstat /tmp/gvt-126032266/loader: no such file or directory
 $ gvt fetch golang.org/x/tools/go/loader
[...]

Only after I entered that temporary directory did I figure out that I was using loader instead of go/loader - for a second I thought something else was going wrong. Perhaps the error given by gvt could be more descriptive if the vcs repository was cloned, but the package in it doesn't exist.

Contributor guide

Research direction
Investigate the fetch command logic in gvt to find where the error message is generated when a package is not found in the cloned repository. The goal is to improve the error message to indicate that the package path might be incorrect, similar to the example given where 'loader' should be 'go/loader'.
Tech stack
go
Domain
clideveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75