{"thread":{"id":"50284","subject":"Improved Error Message","startedAt":"2019-01-22T10:11:07Z","lastAt":"2019-01-22T16:04:58Z","messageCount":2,"participants":["Ralph Martin","Santiago Torres"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"367297","messageId":"EE441A47-48F0-46F3-BF28-C22FDC20169B@cardiff.ac.uk","threadId":"50284","inReplyTo":null,"subject":"Improved Error Message","fromName":"Ralph Martin","fromEmail":"martinrr@cardiff.ac.uk","sentAt":"2019-01-22T10:11:03Z","receivedAt":"2019-01-22T10:11:07Z","isPatch":false,"sender":{"key":"martinrr@cardiff.ac.uk","avatar":null},"body":"While using cask-repair -d from homebrew, I got multiple messages of the form\n\nERROR: Repository not found.\nfatal: Could not read from remote repository.\n\n\nThe author of that command tells me these were issued by git.\nUnfortunately, they are rather unhelpful, as they do not tell the user which repository has not been found.\nCould they please be improved to include the name of the repository which could not be found?"},{"id":"367323","messageId":"20190122155125.6dtajiccvtscrnf4@LykOS.localdomain","threadId":"50284","inReplyTo":"EE441A47-48F0-46F3-BF28-C22FDC20169B@cardiff.ac.uk","subject":"Re: Improved Error Message","fromName":"Santiago Torres","fromEmail":"santiago@nyu.edu","sentAt":"2019-01-22T15:51:25Z","receivedAt":"2019-01-22T16:04:58Z","isPatch":false,"sender":{"key":"santiago@nyu.edu","avatar":"https://avatars.githubusercontent.com/u/3579933?v=4"},"body":"Hi, Ralph.\n\nThis feels like an issue of how homebrew relays information rather than\nwith git:\n\n    santiago at ~ ✔ git clone nonexistent\n    fatal: repository 'nonexistent' does not exist\n    santiago at ~ ✗ git clone https://nonexistent.git\n    Cloning into 'nonexistent'...\n    fatal: unable to access 'https://nonexistent.git/': Could not resolve host: nonexistent.git\n\nHowever, it appears that the error is not that the repository is not\nfound, but rather that the way that the server is set up. \n\nIf you'd like to debug the issue you may want to take at the GIT_TRACE\nenvironment variables. Likewise, cask-repair could relay contextual\ninformation when the error is found (i.e., where was it trying to\nclone), rather than just transparently relaying stderr.\n\nCheers!\n-Santiago.\n\n\nOn Tue, Jan 22, 2019 at 10:11:03AM +0000, Ralph Martin wrote:\n> While using cask-repair -d from homebrew, I got multiple messages of the form\n> \n> ERROR: Repository not found.\n> fatal: Could not read from remote repository.\n> \n> \n> The author of that command tells me these were issued by git.\n> Unfortunately, they are rather unhelpful, as they do not tell the user which repository has not been found.\n> Could they please be improved to include the name of the repository which could not be found?\n"}]}