Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Pass --no-progress argument to multi-pack-index once the option is available #1455

Closed
wilbaker opened this issue Aug 19, 2019 · 1 comment · Fixed by #1517
Closed

Pass --no-progress argument to multi-pack-index once the option is available #1455

wilbaker opened this issue Aug 19, 2019 · 1 comment · Fixed by #1517
Assignees
@wilbaker
Labels
affects: mount-reliability Errors we've seen on Mounts platform: linux platform: macOS platform: windows

Comments

@wilbaker
Copy link
Member

Once VFS4G picks up the changes for microsoft/git#179 it should start passing in --no-progress when it calls git multi-pack-index
@wilbaker
Copy link
Member Author

We have seen reports of out of memory exceptions when the maintenance tasks receive too much data on stderr.

@wilbaker wilbaker mentioned this issue Sep 10, 2019
Merged
@wilbaker wilbaker self-assigned this Sep 10, 2019
This was referenced Sep 10, 2019
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wilbaker wilbaker

Labels
affects: mount-reliability Errors we've seen on Mounts platform: linux platform: macOS platform: windows
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Call multi-pack-index with --no-progress wilbaker/VFSForGit
1 participant
@wilbaker