Support tests in apple silicon and fix NPE in BaseLogStorageTest

[ghost]

I tried to run the project tests for the first time, but they failed. I found 2 reasons and fixed them:
1 - jna.version = 5.5.0 does not support Apple Silicon processors. So I upgraded the version to 5.7.0
2 - BaseLogStorageTest#testTruncatePrefix test failed, it failed with NullPointerException inside ThreadPoolsFactory#runInThread method when accessing ConcurrentHashMap with key == null. To fix this, I added a method to call LogStorageOptions.setGroupId("test"); before running the tests.

Summary by CodeRabbit

• Chores
  • Updated project and module versions to the latest release.
  • Upgraded a key dependency to improve performance and stability.
• Tests
  • Improved log storage test configuration by setting an explicit group identifier.

[sofastack-cla]

Hi @pashchenko8, welcome to SOFAStack community, Please sign Contributor License Agreement!

After you signed CLA, we will automatically sync the status of this pull request in 3 minutes.

[coderabbitai]

Warning

Rate limit exceeded

@sofastack-cla[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 28 minutes and 2 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 9029048 and 0d19b2f.

📒 Files selected for processing (12)

• jraft-core/pom.xml (1 hunks)
• jraft-example/pom.xml (1 hunks)
• jraft-extension/bdb-log-storage-impl/pom.xml (1 hunks)
• jraft-extension/bdb-log-storage-impl/src/test/java/com/alipay/sofa/jraft/storage/impl/BaseLogStorageTest.java (1 hunks)
• jraft-extension/java-log-storage-impl/pom.xml (1 hunks)
• jraft-extension/pom.xml (1 hunks)
• jraft-extension/rpc-grpc-impl/pom.xml (1 hunks)
• jraft-rheakv/pom.xml (1 hunks)
• jraft-rheakv/rheakv-core/pom.xml (1 hunks)
• jraft-rheakv/rheakv-pd/pom.xml (1 hunks)
• jraft-test/pom.xml (1 hunks)
• pom.xml (2 hunks)

Walkthrough

This pull request updates the parent version in numerous Maven POM files from 1.3.15.bugfix to 1.3.16 across multiple modules. Additionally, the root pom.xml updates the project version and bumps the JNA dependency from 5.5.0 to 5.7.0. There is also a minor change in the test file BaseLogStorageTest.java, where a new line explicitly sets the group ID to "test" in the log storage options.

Changes

File(s)	Change Summary
jraft-core/pom.xml, jraft-example/pom.xml, jraft-extension/bdb-log-storage-impl/pom.xml, jraft-extension/java-log-storage-impl/pom.xml, jraft-extension/pom.xml, jraft-extension/rpc-grpc-impl/pom.xml, jraft-rheakv/pom.xml, jraft-rheakv/rheakv-core/pom.xml, jraft-rheakv/rheakv-pd/pom.xml, jraft-test/pom.xml	Updated parent version from 1.3.15.bugfix to 1.3.16.
pom.xml	Updated project version from 1.3.15.bugfix to 1.3.16 and JNA version from 5.5.0 to 5.7.0.
jraft-extension/bdb-log-storage-impl/src/test/java/.../BaseLogStorageTest.java	Added opts.setGroupId("test"); in the newLogStorageOptions() method.

Sequence Diagram(s)

sequenceDiagram
    participant Test as BaseLogStorageTest
    participant Options as LogStorageOptions
    Test->>Options: newLogStorageOptions()
    Note right of Options: Create options instance<br/>Set groupId to "test"
    Options-->>Test: Return configured instance

Loading

Possibly related PRs

• release 1.3.15.bugfix #1141: The changes in the main PR and this PR are related as both involve updates to the version number of the parent project in their respective pom.xml files, specifically transitioning from 1.3.15.bugfix to 1.3.16.

Suggested labels

cla:yes, size/M

Suggested reviewers

• fengjiachun
• killme2008

Poem

Hopping through the code with cheer,
Parent versions leap, new and clear.
A test now sets its group with grace,
Dependencies updated in their place.
I’m a bunny of code—let’s hop to a brighter space!

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.