-
Notifications
You must be signed in to change notification settings - Fork 113
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
Fuzzing tests for ledger rpc #403
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
|
preston-evans98
force-pushed
the
theo/tests-rpc
branch
from
June 20, 2023 20:45
ce68e9c
to
f6e514e
Compare
preston-evans98
force-pushed
the
theo/tests-rpc
branch
from
June 20, 2023 20:48
f6e514e
to
b8b27e3
Compare
* fix(sov-db): serialize u64 keys as big-endian * style(sov-db): formatting fix * test(demo-rollup): proptest regressions * test(demo-rollup): larger batches, json utils * fix(sov-db): serialize SlotByNumber, EventByNumber as big-endian The big-endian fix for u64_wrapper! wasn't applied to all relevant types. I've made the following changes: * Renamed define_table_with_u64_wrapper_keys -> define_table_with_seek_key_codec to not be u64_wrapper! -specific. * I replaced the u64_wrapper! specific logic inside said macro to use * big-endian bincode instead, in preparation for using it for different and more complex types. Not yet used for anything other than u64_wrapper!. * I removed the blanked implementation of SeekKeyEncoder for all KeyEncoder's, so that implementors have to opt-in, providing a fail-safe. In the future we'll explore better type safety mechanisms. * Update define_table_with_seek_key_codec macro comment
citizen-stig
reviewed
Jul 3, 2023
neysofu
approved these changes
Jul 3, 2023
Co-authored-by: Nikolai Golub <[email protected]>
citizen-stig
approved these changes
Jul 3, 2023
neysofu
approved these changes
Jul 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements fuzzing tests for ledger rpc. The fuzzing api is used to generate random test data for the ledger db and random queries to test the ledger rpc api.
Linked Issues
Testing
Some tests have been added to the test_rpc.rs folder.