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.

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

Recompressing 'tree-sitter-haskell-74c278e7a2ef8d7d': 262.35 MB => #125

Open
ket000 opened this issue Jan 2, 2023 · 4 comments
Open

Recompressing 'tree-sitter-haskell-74c278e7a2ef8d7d': 262.35 MB => #125

ket000 opened this issue Jan 2, 2023 · 4 comments

Comments

@ket000
Copy link

ket000 commented Jan 2, 2023

On my old laptop, the commnd

cargo cache -e is stuck for more than 3 hours.

Recompressing 'tree-sitter-haskell-74c278e7a2ef8d7d': 262.35 MB =>

It has below cpu

Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz
and 4 gb ram.

@matthiaskrgr
Copy link
Owner

Oh I think i vaguely remember some problem with tree-sitter.
There might be an insane amount of objects in its git repo causing some kind if exponential blowup when compressing via "git gc", but im also not sure if there's anything i can do about it (im on a dual core system as well, but with 16 gigs of ram)

@ket000
Copy link
Author

ket000 commented Jan 2, 2023

Is there a way to skip compressing certain repo in case it takes more than x amount of time or create manual ignore list. At least this will complete the process.

@matthiaskrgr
Copy link
Owner

I don't think cargo-cache can skip particular sources right now, a hardcoded ignore list should be easy, some kind of timeout might be tricky but also doable.

Anyway you could just rm the tree-sitter-haskell... directory and run -e again, the git repo will be recloned by cargo as soon as it's needed again 😅

@ket000
Copy link
Author

ket000 commented Jan 2, 2023

Thanks for the suggestion. I will try that and post update here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants