-
Notifications
You must be signed in to change notification settings - Fork 225
Big objects in the repo and overall repo size #339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, You seem to be cloning the docs branch as well (which is huge). |
Hi! I've been looking into this a bit as well, and it seems we have huge things in the repo history, a regular clone (no options) only fetches the master branch by default as far as I can tell, for comparison see the second command with branch specified:
With the help of git sizer:
The largest object [4]:
🤔
Those tmp folders doesn't look right I'm not sure yet where the data is hiding, but I think this needs further investigation. Thanks @little-arhat for bringing it to our attention! |
Given that last released version (0.5.5) is not compatible with recent cortex-m, users who want to stay on cortex-m >= 0.7 have to use git version, and given repo sizes (Cargo itself doesn't support shallow clones it seems: rust-lang/cargo#1171) |
Issue cleanup: Please reopen if this is still active. |
I would say this is still active, as no progress was made neither in cargo (to support shallow clones) nor here (to cleanup history) :) |
Reopening, I think especially true for all testing out the latest alpha with a git-upstream. The support for shallow clones is cargo is of course outside our reach, leaving the option to somehow trim the history without breaking too much. Suggestions are welcome, I'll try to dig deeper into this. |
@little-arhat Please test this again after yesterday's cleanup. For details see the discussion in the RFC repo linked. |
After a few commits to master, including documentation rebuilds and publishing I get this much nicer total repo size:
So I consider this resolved, if not, please reopen. |
Hello!
I'm using nigtly and therefore have to use rtic from repo. I did
cargo update
recently and noticed that rtic-rs update took much longer thancortex-m
.I used script to find large objects in the repo:
Unfrotunately, I couldn't find origin commit with
git log --all --pretty=format:%H | xargs -n1 -I% sh -c "git ls-tree % | grep -q 08c4a85f54d6b3c9fb278e4151f592015b9313c9 && echo %"
.The text was updated successfully, but these errors were encountered: