-
Notifications
You must be signed in to change notification settings - Fork 59
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
Temporarily revert v0.6.7 changes #9
Conversation
This reverts commit 0c9484c.
Signed-off-by: Thane Thomson <[email protected]>
Signed-off-by: Thane Thomson <[email protected]>
Signed-off-by: Thane Thomson <[email protected]>
Signed-off-by: Thane Thomson <[email protected]>
Signed-off-by: Thane Thomson <[email protected]>
Signed-off-by: Thane Thomson <[email protected]>
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 have the impression this PR has been produced mechanically/methodically, so feel free to disregard any of my remarks if addressing them means hindering the mechanical part of it.
An exception is, I think, the one about the octal notation
@@ -25,7 +25,7 @@ func NewBadgerDB(dbName, dir string) (*BadgerDB, error) { | |||
// the final directory to use for the database. | |||
path := filepath.Join(dir, dbName) | |||
|
|||
if err := os.MkdirAll(path, 0o755); err != nil { |
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.
Are we sure about this change?
Last time I was something similar was (I think) in one of Jacob's PR's, but his change also came with a change in the library used.
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.
The 0o755
-> 0755
change? If so, it's just a convention automatically set by the formatter. There are 3 different formats for octal literals that mean the same thing according to the Go spec: https://go.dev/ref/spec#Integer_literals
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.
My current plan is to clean up the repo prior to cutting a v0.6.8 release so as to update the linter config, etc. to harmonize with what we have in the CometBFT repo.
Signed-off-by: Thane Thomson <[email protected]>
Closes #8
This is unfortunately not a simple revert, but it reverts all of the core logic/dependency changes after the v0.6.6 release.