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

Move faulty assert #4533

Merged
merged 1 commit into from
May 23, 2023
Merged

Move faulty assert #4533

merged 1 commit into from
May 23, 2023

Conversation

ximinez
Copy link
Collaborator

@ximinez ximinez commented May 22, 2023

High Level Overview of Change

Does what it says on the tin. One of the asserts introduced in #4319 (66627b2) was put in the wrong place, but wasn't triggered unless shards were configured.

This pull request, if merged, moves the assert to the right place, and updates it to ensure correctness.

Note that normally asserts are only checked in debug builds, so release packages will not be affected.

Type of Change

  • [X ] Bug fix (non-breaking change which fixes an issue)

Test Plan

  • Run a debug build with shards configured.
  • Wait until rippled downloads some shards.
  • May need to restart once the shard is downloaded, (I'm not sure, and haven't reproduced yet.)

Before this fix:

  • rippled will assert in Shard.cpp line 693.

After this fix:

  • rippled will not assert.

@intelliot intelliot requested review from gregtatcam and drlongle May 23, 2023 00:55
@drlongle
Copy link
Contributor

LGTM!

Copy link
Collaborator

@gregtatcam gregtatcam left a comment

Choose a reason for hiding this comment

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

👍 LGTM

@intelliot intelliot merged commit 32f8ae1 into XRPLF:develop May 23, 2023
@intelliot intelliot mentioned this pull request May 23, 2023
1 task
@ximinez ximinez deleted the shard-assert branch May 24, 2023 19:30
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.

4 participants