Skip to content

Follow-up to #3481: Assert we migrated all exactly all keys #3491

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

Closed
wants to merge 1 commit into from

Conversation

tnull
Copy link
Contributor

@tnull tnull commented Dec 17, 2024

Follow-up to #3481

Previously, we'd only check that the number of migrated keys and that the migrated data is correct. Here, we also check that all the Previously-written keys are migrated as expected.

@tnull tnull mentioned this pull request Dec 17, 2024
2 tasks
Previously, we'd only check that the number of migrated keys and that
the migrated data is correct. Here, we also check that all the
Previously-written keys are migrated as expected.
@tnull tnull force-pushed the 2024-12-3481-followup branch from 33d3a44 to f85e96d Compare December 17, 2024 11:13
@TheBlueMatt
Copy link
Collaborator

Oops, sorry. This wasn't all that critical, but I went ahead and shoved it in #3490 (which wasn't intended as a fuzzing PR at all until I started testing...)

@tnull
Copy link
Contributor Author

tnull commented Dec 18, 2024

Oops, sorry. This wasn't all that critical, but I went ahead and shoved it in #3490 (which wasn't intended as a fuzzing PR at all until I started testing...)

Okay.

@tnull tnull closed this Dec 18, 2024
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