Re: Improved Error Message

From: Santiago Torres <santiago@nyu.edu>
Date: Jan 22, 2019, 15:51 UTC
Message-ID: <20190122155125.6dtajiccvtscrnf4@LykOS.localdomain>
In-Reply-To: <EE441A47-48F0-46F3-BF28-C22FDC20169B@cardiff.ac.uk>

Hi, Ralph.

This feels like an issue of how homebrew relays information rather than with git:

    santiago at ~ ✔ git clone nonexistent
    fatal: repository 'nonexistent' does not exist
    santiago at ~ ✗ git clone https://nonexistent.git
    Cloning into 'nonexistent'...
    fatal: unable to access 'https://nonexistent.git/': Could not resolve host: nonexistent.git

However, it appears that the error is not that the repository is not found, but rather that the way that the server is set up.

If you'd like to debug the issue you may want to take at the GIT_TRACE environment variables. Likewise, cask-repair could relay contextual information when the error is found (i.e., where was it trying to clone), rather than just transparently relaying stderr.

Cheers! -Santiago.

On Tue, Jan 22, 2019 at 10:11:03AM +0000, Ralph Martin wrote:

Show 9 quoted lines

> While using cask-repair -d from homebrew, I got multiple messages of the form
> 
> ERROR: Repository not found.
> fatal: Could not read from remote repository.
> 
> 
> The author of that command tells me these were issued by git.
> Unfortunately, they are rather unhelpful, as they do not tell the user which repository has not been found.
> Could they please be improved to include the name of the repository which could not be found?