Add error message when git returns non-0 for fetch#13449
Add error message when git returns non-0 for fetch#13449tomberek merged 3 commits intoNixOS:masterfrom
Conversation
|
@tomberek thanks for the review. One of the more suprising ones, is that in the presence of "packed-refs", the git fetcher caching functionality breaks. When packed-refs are enabled this is not present and so code has to be refetched. This was previously hidden before because the code previously would silently fail on the Is there an issue for the failure to cache in the presence of packed-refs ? |
|
MacOS failures are "nix-daemon-compat-tests> daemon died unexpectedly" |
Users have complained that fetchGit is flaky however the culprit is likely that `git fetch` was unable itself to download the repository for whatever reason (i.e. poor network etc..) Nothing was checking the status of `git fetch` and the error message that would eventually surface to the users were that the commit was not found. Add explicit error checking for status code from `git fetch` and return a message earlier on to indicate that the failure was from that point. fixes NixOS#10431
Users have complained that fetchGit is flaky however the culprit is likely that
git fetchwas unable itself to download the repository for whatever reason (i.e. poor network etc..)Nothing was checking the status of
git fetchand the error message that would eventually surface to the users were that the commit was not found.Add explicit error checking for status code from
git fetchand return a message earlier on to indicate that the failure was from that point.fixes #10431
validation
This message is different from the previous one that looks like the following when the commit is checked to be in the repo which was causing confusion.
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.