-
Notifications
You must be signed in to change notification settings - Fork 40
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
chore: Make Cid versions consistent #57
Conversation
Code is dead, and untested - consider removal (is half used by a single unit which only counts the keys, but doesn't assert their values)
44e0dd9
to
36b5856
Compare
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.
All LGTM 👍
side note: I'm always amused seeing sprinkled in your PRs, a trickle effect of slowly removing dead and commented out legacy code
Nice, will rename the commit and then merge RE: sidenote - definitely prefer dripping stuff in as opposed to the hassle/risk of doing it all at once (although it doesn't play as nicely with squashing commits on merge sadly) |
36b5856
to
c909037
Compare
* Rename test file to go runs tests * Remove commented out code * Remove unused property * Return V0 Cids from blockstore.AllKeysChan Code is dead, and untested - consider removal (is half used by a single unit which only counts the keys, but doesn't assert their values) * Use v1 Cids throughout the codebase
Closes #49
Review contains some small tweaks/fixes, followed by a proposed update to modifiy all our non-dockey Cids to v1 (from v0). Dockeys are already using v1 Cids (I think).
This will impact existing databases considerably and doubt we can rely on an existing migrations (such as when updating badger versions). I do not know if we need to actively do anything for this, or if our current users are happy to just nuke and rebuild their databases - please let me know if more is required here.
To do: