[BUG]: repository too large
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- git
- Domain
- developer-experience
Research direction
Start by measuring the repository contents and Git history to identify what accounts for the 650MB clone. Review the issue discussion for any proposed approach or constraints. Done means local-development materials remain available while the repository can be cloned substantially faster on limited internet connections.
Written by the indexing model from the issue text.
Description
Is this a duplicate?
- I confirmed there appear to be no duplicate issues for this bug and that I agree to the Code of Conduct
Describe the bug
git clone for local development requires 650MB download. This is not something that one can do at conferences with shotty internet where the material is presented.
Steps to reproduce
git clone
Expected behavior
faster download
Actual behavior
very slow download
Environment
No response
Additional context
No response
- Dominant language
- Jupyter Notebook
- Stars
- 2.1k
- Forks
- 358
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/accelerated-computing-hub
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NVIDIA/accelerated-computing-hub#294 ·
Maintainers usually reply within 4 days
-
Remove obsolete port-binding rewrite from brev/dev-start.bashPossibly taken @MaxFreedomPollard claimed this 43 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA/accelerated-computing-hub#216 ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NVIDIA/accelerated-computing-hub#171 ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
NVIDIA/accelerated-computing-hub#89 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
NVIDIA/accelerated-computing-hub#85 ·
Maintainers usually reply within 4 days
All issues in NVIDIA/accelerated-computing-hub
Similar issues
-
diagram-bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
enhapu-afk/omaspec#4 ·
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LucasSantana-Dev/Lucky#2945 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
earthtojake/text-to-cad#758 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
colbymchenry/codegraph#3223 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
r-afael/better-yt-recommendations#36 ·
Maintainers usually reply within 1 day