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

Optimized Slasher Database Methods #8805

Merged
merged 3 commits into from
Apr 23, 2021
Merged

Optimized Slasher Database Methods #8805

merged 3 commits into from
Apr 23, 2021

Conversation

rauljordan
Copy link
Contributor

What type of PR is this?

Feature

What does this PR do? Why is it needed?

This PR adds core slasher database methods from #8331. All code in this PR has already been reviewed and merged into branch feature/slasher already, but we are merging this into develop for an easier review of the feature branch later.

Which issues(s) does this PR fix?

Part of #8331

@rauljordan rauljordan requested a review from a team as a code owner April 23, 2021 15:10
@rauljordan rauljordan merged commit 8cda50f into develop Apr 23, 2021
@delete-merged-branch delete-merged-branch bot deleted the slasher-core-db branch April 23, 2021 17:06
const (
// DatabaseFileName is the name of the beacon node database.
DatabaseFileName = "slasher.db"
boltAllocSize = 8 * 1024 * 1024
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a comment to explain what this is please?

"github.com/prysmaticlabs/prysm/shared/testutil/require"
)

// setupDB instantiates and returns a Store instance.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to test some of the other things in kv.go? Perhaps testing the buckets were created.

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

Successfully merging this pull request may close these issues.

3 participants