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

Problem: rocksdb is out of date #1378

Merged
merged 4 commits into from
Apr 9, 2024

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Apr 8, 2024

Solution:

  • upgrade to v8.11.3

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

  • Have you read the CONTRIBUTING.md?
  • Does your PR follow the C4 patch requirements?
  • Have you rebased your work on top of the latest master?
  • Have you checked your code compiles? (make)
  • Have you included tests for any non-trivial functionality?
  • Have you checked your code passes the unit tests? (make test)
  • Have you checked your code formatting is correct? (go fmt)
  • Have you checked your basic code style is fine? (golangci-lint run)
  • If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
  • If your changes affect the client infrastructure, have you run the integration test?
  • If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
  • If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
  • If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features
    • Upgraded RocksDB to version v8.11.3 for improved store functionality.
  • Refactor
    • Updated dependencies and configurations to support the new RocksDB version.
    • Modified build and installation steps for macOS and Linux to accommodate RocksDB changes.
  • Chores
    • Updated the linting process to exclude specific build tags, enhancing code quality checks.

@yihuang yihuang requested a review from a team as a code owner April 8, 2024 23:49
@yihuang yihuang requested review from JayT106 and calvinaco and removed request for a team April 8, 2024 23:49
Copy link
Contributor

coderabbitai bot commented Apr 8, 2024

Walkthrough

The project has seen substantial improvements, highlighted by upgrading rocksdb to version v8.11.3 for enhanced performance. This update extends to various areas such as dependency management, build configurations, and linting processes, reinforcing the project's foundation for increased efficiency and resilience.

Changes

Files Change Summary
CHANGELOG.md, nix/rocksdb.nix Upgraded rocksdb to v8.11.3, including related build configuration and documentation updates.
gomod2nix.toml Updated github.com/linxGnu/grocksdb to version v1.8.14 with a new hash.
.github/workflows/lint.yml Modified linting by excluding --build-tags for memiavl and store directories.
integration_tests/configs/upgrade-test-package.nix Updated fetched flake to yihuang/cronos with a new commit hash and added a GitHub pull request reference.

🐇✨
In the realm of code, where the bits frolic and play,
A rabbit hopped forth, bringing updates today.
With a leap and a bound, rocksdb did upgrade,
And the linting tools, a smoother path they made.
So here's to the changes, both big and small,
May our code run swift, may it stand tall.
🌟🐾


Recent Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 384b59d and 5fb9b7b.
Files selected for processing (1)
  • integration_tests/configs/upgrade-test-package.nix (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • integration_tests/configs/upgrade-test-package.nix

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

CHANGELOG.md Outdated Show resolved Hide resolved
@yihuang yihuang requested a review from mmsqe April 8, 2024 23:50
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 1aea999 and a4e59d5.
Files ignored due to path filters (8)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum
  • memiavl/go.mod is excluded by !**/*.mod
  • memiavl/go.sum is excluded by !**/*.sum
  • store/go.mod is excluded by !**/*.mod
  • store/go.sum is excluded by !**/*.sum
  • versiondb/go.mod is excluded by !**/*.mod
  • versiondb/go.sum is excluded by !**/*.sum
Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • gomod2nix.toml (1 hunks)
  • nix/rocksdb.nix (4 hunks)
Additional comments not posted (7)
nix/rocksdb.nix (6)

23-29: Updated version to 9.0.0 looks good. Please ensure the provided hash matches the expected value for this version.


44-46: Addition of -faligned-allocation for Clang compilers is a good practice for memory alignment. Please ensure thorough testing on platforms using Clang.


71-86: Adjustments in postPatch for gcc-13 build failures and zstd_INCLUDE_DIRS are noted. Please verify these patches are still necessary for version 9.0.0.


87-92: preInstall steps for macOS and Linux look well thought out. Please ensure testing on both platforms to confirm expected behavior.


102-116: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [99-105]

postFixup adjustments for .pc file paths and shared libraries on Darwin are important for integration. Please verify paths and behavior on Darwin.


111-111: Updating the changelog link to match the new version is a good practice for keeping users informed.

gomod2nix.toml (1)

400-401: The update to the "github.com/linxGnu/grocksdb" module version and hash appears correct and aligns with the PR's objective to update dependencies. Ensure the hash value has been verified for security purposes.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between a4e59d5 and 14b6b21.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Additional comments not posted (1)
CHANGELOG.md (1)

7-7: The entry for upgrading rocksdb to v9.0.0 is correctly formatted and placed, maintaining consistency with the rest of the changelog. Good job on keeping the documentation up-to-date with the project changes.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 1aea999 and 25ee8d2.
Files ignored due to path filters (4)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum
  • versiondb/go.mod is excluded by !**/*.mod
  • versiondb/go.sum is excluded by !**/*.sum
Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • gomod2nix.toml (2 hunks)
  • nix/rocksdb.nix (4 hunks)
Files skipped from review as they are similar to previous changes (2)
  • gomod2nix.toml
  • nix/rocksdb.nix

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 25ee8d2 and 93a0f4e.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Additional comments not posted (1)
CHANGELOG.md (1)

7-7: The changelog entry correctly documents the upgrade of rocksdb to v9.0.0. This update aligns with the PR's objective and maintains consistency with the format and structure of previous entries in the changelog.

go.mod Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 93a0f4e and 11f3a5b.
Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • nix/rocksdb.nix (4 hunks)
Files skipped from review as they are similar to previous changes (1)
  • nix/rocksdb.nix

@yihuang yihuang enabled auto-merge April 9, 2024 01:43
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 11f3a5b and 40df221.
Files selected for processing (1)
  • .github/workflows/lint.yml (1 hunks)
Additional comments not posted (2)
.github/workflows/lint.yml (2)

53-53: Verify the intention behind removing --build-tags $BUILD_TAGS for linting the memiavl directory.

Ensure that removing the build tags does not inadvertently exclude important code from the linting process.


55-55: Verify the intention behind removing --build-tags $BUILD_TAGS for linting the store directory.

Ensure that removing the build tags does not inadvertently exclude important code from the linting process.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 1aea999 and a35dd7a.
Files ignored due to path filters (4)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum
  • versiondb/go.mod is excluded by !**/*.mod
  • versiondb/go.sum is excluded by !**/*.sum
Files selected for processing (4)
  • .github/workflows/lint.yml (1 hunks)
  • CHANGELOG.md (1 hunks)
  • gomod2nix.toml (2 hunks)
  • nix/rocksdb.nix (4 hunks)
Files skipped from review as they are similar to previous changes (3)
  • .github/workflows/lint.yml
  • gomod2nix.toml
  • nix/rocksdb.nix

CHANGELOG.md Show resolved Hide resolved
@mmsqe
Copy link
Collaborator

mmsqe commented Apr 9, 2024

should we align memiavl as well? but do we do any db migrate to avoid the invalid nonce err

@yihuang
Copy link
Collaborator Author

yihuang commented Apr 9, 2024

should we align memiavl as well?

they only depends on grocksdb indirectly, not necessary to update manually.

but do we do any db migrate to avoid the invalid nonce err

this is needed.

@mmsqe
Copy link
Collaborator

mmsqe commented Apr 9, 2024

this is needed.

I got invalid nonce bump from 8.1.1 to 8.3.2

@yihuang
Copy link
Collaborator Author

yihuang commented Apr 9, 2024

this is needed.

I got invalid nonce bump from 8.1.1 to 8.3.2

yeah, still investigating.

yihuang added 2 commits April 9, 2024 16:29
Solution:
- upgrade to v8.11.3

grocksdb v1.8.14

changelog

fix build

Update CHANGELOG.md

Signed-off-by: yihuang <huang@crypto.com>

try fix
@yihuang yihuang added this pull request to the merge queue Apr 9, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Apr 9, 2024
@yihuang yihuang enabled auto-merge April 9, 2024 10:46
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.

2 participants