app/obolapi: ignore empty partial signatures #50
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
API will return partial signatures iff there are at least threshold of them, which also means we could find `null`'s in the response. Since the partial signatures array returned by the API maps 1:1 with the corresponding share index, we need to ignore empty ones to keep going with the aggregation process. We still error if the signature is longer than 0 bytes but no more than 2. Added a test case to cover the issue as well.
|
pinebit
approved these changes
Jan 12, 2024
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.
API will return partial signatures iff there are at least threshold of them, which also means we could find
null's in the response.Since the partial signatures array returned by the API maps 1:1 with the corresponding share index, we need to ignore empty ones to keep going with the aggregation process.
We still error if the signature is longer than 0 bytes but no more than 2.
Added a test case to cover the issue as well.
category: bug
ticket: none