NVIDIA / NVIDIA/edk2-nvidia

Unable to pull the repository code properly.

Open
#145 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
145
Forks
66
PR merge metrics
No merged PRs in 30d

Description

root@wpces-virtual-machine:/home/wpces/Downloads# edkrepo clone nvidia-uefi NVIDIA-Platforms main
Syncing the global manifest repository: /root/.edkrepo/edk2-edkrepo-manifest-main
Syncing the global manifest repository: /root/.edkrepo/nvidia
Verifying the global manifest repository entry for project: NVIDIA-Platforms

Cloning from: https://github.com/NVIDIA/edk2.git
Cloning from: https://github.com/NVIDIA/edk2-non-osi.git
Cloning from: https://github.com/NVIDIA/edk2-platforms.git
Cloning from: https://github.com/NVIDIA/edk2-infineon.git
Cloning from: https://github.com/NVIDIA/edk2-redfish-client.git
Cloning from: https://github.com/NVIDIA/edk2-nvidia.git
Cloning from: https://github.com/NVIDIA/edk2-nvidia-non-osi.git
Cloning from: https://android.googlesource.com/platform/external/avb
The git command: git clone --no-checkout --progress -v https://android.googlesource.com/platform/external/avb /home/wpces/Downloads/nvidia-uefi/edk2-nvidia/Silicon/NVIDIA/Library/AvbLib/libavb failed to complete successfully with the following errors.

root@wpces-virtual-machine:/home/wpces/Downloads#

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported edkrepo clone nvidia-uefi NVIDIA-Platforms main command and follow the clone of https://android.googlesource.com/platform/external/avb into edk2-nvidia/Silicon/NVIDIA/Library/AvbLib/libavb. Inspect the underlying git error and edkrepo's clone handling. Done means the repository clone completes successfully or the failure is reported with an actionable cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.