Closed killme2008 closed 2 weeks ago
[!WARNING]
Rate limit exceeded
@killme2008 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 21 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](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between 3ed6dcc6230d4643cc64e460133a791143fbce62 and 2245e2bf4ad0c5d7f5879034f431578836971baa.
The NodeTest.java
file has been updated to include enhanced exception handling in the testChangePeersChaosApplyTasks
method. This enhancement involves the addition of a try-catch block around the future.get()
calls, enforcing a timeout of 20 seconds and providing appropriate handling for TimeoutException
. The restructuring aims to ensure robustness and reliability in handling futures and timeouts during peer change operations.
File | Summary |
---|---|
jraft-core/src/test/.../NodeTest.java |
Enhanced testChangePeersChaosApplyTasks with try-catch handling around future.get() calls and restructured loop for robust timeout and TimeoutException handling. |
Amidst the code, in tests so bright, A timeout shield, we set alight. π With futures called and errors tamed, Stability and order claimed. π°οΈπ In the chaos peers once knew, Now smoother paths, we pursued. ππ
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?
A fatal error when testing LogitLogStorage
:
>>>>>>>>>>>>>>> Start test method: testInstallLargeSnapshot
Start ensureSame, waitTimes=-1
End ensureSame, waitTimes=-1
Node<10.1.0.100:5004> saved snapshot into /tmp/jraft_test_789104793204/10.1.0.100_5004/snapshot/temp/data
Node<10.1.0.100:5004> saved snapshot into /tmp/jraft_test_789104793204/10.1.0.100_5004/snapshot/temp/data
Node<10.1.0.100:5006> loaded snapshot from /tmp/jraft_test_789104793204/10.1.0.100_5006/snapshot/snapshot_2001/data
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007effd98391ca, pid=20721, tid=0x00007eff3d7ff640
#
# JRE version: OpenJDK Runtime Environment (Zulu 8.78.0.19-CA-linux64) (8.0_412-b08) (build 1.8.0_412-b08)
# Java VM: OpenJDK 64-Bit Server VM (25.412-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x8391ca]3,0001,Start ensureSame\u002C waitTimes=-1\n
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/runner/work/sofa-jraft/sofa-jraft/jraft-extension/java-log-storage-impl/hs_err_pid20721.log
End ensureSame, waitTimes=-1
#
# If you would like to submit a bug report, please visit:
# http://www.azul.com/support/
#
Aborted (core dumped)
Motivation & Modification
As seen in CI https://github.com/sofastack/sofa-jraft/actions/runs/9543270248/job/26299583757
It failed at:
Looks like it's an expected error. So just assert the error message when raising exceptions in
chaosSplittingCheckData
.Result:
Fixes #.
If there is no issue then describe the changes introduced by this PR.
Summary by CodeRabbit