Skip to content

Conversation

@patrick-ogrady
Copy link
Contributor

@patrick-ogrady patrick-ogrady commented Jul 25, 2023

Alternative: #1762

Why this should be merged

Might resolve: #1760

How this works

We ensure that the sync target cannot be updated while we are determining whether to re-add completed workItems to the queue or mark as processed.

How this was tested

HyperSDK: ava-labs/hypersdk#278

@patrick-ogrady patrick-ogrady changed the title [x/sync] Update sync locking (approach 2) [x/sync] Update target locking (approach 2) Jul 25, 2023
@StephenButtolph StephenButtolph marked this pull request as ready for review July 26, 2023 00:45
@StephenButtolph StephenButtolph added this to the v1.10.6 milestone Jul 26, 2023
@StephenButtolph StephenButtolph added bug Something isn't working merkledb labels Jul 26, 2023
@StephenButtolph StephenButtolph changed the title [x/sync] Update target locking (approach 2) [x/sync] Update target locking Jul 26, 2023
zap.Binary("start", work.start),
zap.Binary("end", largestHandledKey),
zap.Stringer("rootID", rootID),
zap.Bool("stale", stale),
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will be a super useful new log IMO (when I'm hammering this)

@StephenButtolph StephenButtolph merged commit ef023d2 into dev Jul 26, 2023
@StephenButtolph StephenButtolph deleted the update-sync-locking-2 branch July 26, 2023 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working merkledb

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants