-
Notifications
You must be signed in to change notification settings - Fork 550
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
NPE during cleanup up of big blobs #37
Comments
Interesting - looks like The BFG is passing JGit a null object id, which is pretty surprising. Is the repo publicly available for me to reproduce this? |
Failing that, could you send me the output of this command executed in your repositories directory:
|
Hello Roberto,
|
I have tried to remove all the tags from the --protect-blobs-from option keeping only branches and master. And it works fine. |
@sgandon, you're completely right, this was a bug in The BFG - thanks for reporting it. It only occurred with 'annotated' tags - tag objects that contain full tagging metadata like author & message - which is why I hadn't spotted it before. The fix is in the soon-to-be-available v1.11.2 release of The BFG. Thanks again for getting in contact! |
You are most welcome, you product is a killer especially because of the speed performance. |
Ah no worries, the new v1.11.2 release is already available and you can download it here: http://rtyley.github.io/bfg-repo-cleaner/ There's a delay of a few hours between me 'releasing' a release and the new artifact being available for download - this delay is the Maven Central 'sync' delay, where artifacts are copied from feeder repositories (like oss.sonatype.org) to Maven Central proper. I don't currently have an RSS feed or Twitter account for releases - for most people, the need for The BFG is a one-off, they generally don't need to be kept up to date with updates! |
Thank for everything, I'll test it right away. |
Hi Roberto,
When removing blobs bigger than 1MB in my repo I get the following NPE.
I have not had a look at your code so I am not sure if it comes from JGit or BFG.
You'll find at the bottom the command line used that generated this exception.
here is the command line used to launch BFG.
The text was updated successfully, but these errors were encountered: