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

FSCK in gitoxide-core #287

Closed
4 tasks done
Byron opened this issue Dec 29, 2021 · 0 comments
Closed
4 tasks done

FSCK in gitoxide-core #287

Byron opened this issue Dec 29, 2021 · 0 comments

Comments

@Byron
Copy link
Owner

Byron commented Dec 29, 2021 •
edited

Essentially a verify_integrity() on git_odb::Store, run integrity checks on all indices/multi-indices and summarize the results.
@Byron Byron created this issue from a note in Collaboration Board (To do) Dec 29, 2021
@Byron Byron moved this from To do to In progress in Collaboration Board Jan 2, 2022
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
change!: cleanup and unify verify_integrity() method signature (#287)
91d0476 
Previously they used many different ways of handling their parameters
despite all boiling down to calling the same 'index::File::traverse()`
method.

This allows for more reuse of `Options` structs and generally makes
clearer how these optinos are used.
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
frame for interity check on object store (#287)
b5dd059
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
Adjustments to deal with changes to git-pack/git-odb (#287)
fcf8fde
@Byron Byron mentioned this issue Jan 2, 2022
Merged
6 tasks
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
change!: Improve method signatures of cache::Tree::* (#287)
a79a7fb
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
Don't reset generations, instead make them match the current one (#287)
1d995ef 
That way, even empty slots can be identified as 'changed' compared to
some older index even if they are empty.

This makes it consistent, as indices refer to occupied slots only and
protect themselves from changes using the generation flag, which usually
comes first.
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
refactor (#287)
6c06659 
Re-use the index::integrity::Options for multi_index options as it's
exactly the same.
This opportunty was missed the previous we simplified these signatures.
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
First basic validation of all packs within an odb store (#287)
d63176f
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
frame for loose-db validation (#287)
a24307d
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
bare-bones loose object integrity check (#287)
3dfec81
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
support for loose object statistics in odb store (#287)
53d835a
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
Very rough version of repository verification (#287)
d240ab3
Byron added a commit that referenced this issue Jan 2, 2022
@Byron
Very rough version of repository verification (#287)
80a4a7a
@Byron Byron moved this from In progress to To do in Collaboration Board Jan 2, 2022
@Byron Byron moved this from To do to In progress in Collaboration Board Jan 3, 2022
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
Test to reproduce ref-delta forward references and the issue it poses…
7db7195 
… for index traversal (#287)
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
refactor (#287)
38426a1
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
fix: Allow resolution of in-pack ref-deltas (#287)
84ade1d 
This finally allows delta tree caches to be used on typical small packs
returned by GitHub.
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
refactor (#287)
831397c 
Remove VecDeque in favor of two vecs which will keep their indices
stable no matter what, while making much clearer what's happening.

It's surprising I wasn't able to do this refactor the first time around
and shows how hard it was to understand (for me) :D.
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
better verify progress printing (#287)
4a464f2
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
smart-release now actually shows the time between releases (#287)
cd8d343
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
upgrade to prodash 17 (#287)
47860b7
@Byron Byron closed this as completed Jan 3, 2022
Collaboration Board automation moved this from In progress to Done Jan 3, 2022
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
way nicer progress messages for repo verification (#287)
4b4f9f8
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
share and pass cli arguments for pack verification (#287)
db43e47
Byron added a commit that referenced this issue Jan 3, 2022
@Byron
basic output for 'repo verify' json only (#287)
9f8d61f
Byron added a commit that referenced this issue Jan 4, 2022
@Byron
lower-case json fields for consistency (#287)
f6c0e6d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Byron