-
Notifications
You must be signed in to change notification settings - Fork 86
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
Delete corrupted git repos #494
Conversation
crev-lib/src/local.rs
Outdated
@@ -1386,3 +1396,17 @@ fn local_is_send_sync() { | |||
fn is<T: Send + Sync>() {} | |||
is::<Local>(); | |||
} | |||
|
|||
|
|||
fn rm_directory(path_to_delete: &Path) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm always a bit scared seeing such functions. Get we make add some check here, that the directory is a subdirectory (has a prefix) of the dirs we expect to delete stuff in?
What's with you changes never passing |
I think rustfmt is a deeply flawed tool that often makes code less readable, and therefore is unfit to be applied unconditionally to everything. |
Oooooh. :D |
what I love about rustfmt is no more arguing about code style: A project sets it once and can forget about it. Or every organization wide code looks the same, no matter which project. Best invention since sliced bread, IMHO ^^ Also I can write code in the IDE without having to spend brain cycles on indentation / formatting at all and concentrate on the logic. rustfmt runs automatically on save. For me it's a huge productivity win in the end, I can concentrate on the important stuff during code review. Anyway, on a more serious side:
Or is the code just supposed to clean completely corrupted (=borked) git repos? Current output:
|
This error is about not being able to fetch given repository, not that it is corrupted locally. I'm not sure what to do about it. Probably hide behind some toggle. Seems like it bother people, but on the other hand it is a useful information in case someone was wondering why they can't get data from a certain id/url. PRs welcome. :) |
For these I think some kind of exponential backoff would be appropriate. Remember how many fetches failed, and then don't try to fetch them for a while. |
No description provided.