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

Return error for num == 0 for bls_g1_weighted_sum, bls_g2_weighted_sum and bls_pairing #1953

Closed
heifner opened this issue Dec 6, 2023 · 1 comment · Fixed by #1954 or #1956
Closed
Assignees
Labels
consensus 👍 lgtm OCI Work exclusive to OCI team

Comments

@heifner
Copy link
Member

heifner commented Dec 6, 2023

Return error for num == 0 for bls_g1_weighted_sum, bls_g2_weighted_sum, and bls_pairing.

AntelopeIO/cdt#221 (review)

@heifner heifner added this to the Leap v5.0.0 milestone Dec 6, 2023
@heifner heifner self-assigned this Dec 6, 2023
@enf-ci-bot enf-ci-bot moved this to Todo in Team Backlog Dec 6, 2023
@heifner heifner added 👍 lgtm and removed triage labels Dec 6, 2023
@heifner
Copy link
Member Author

heifner commented Dec 6, 2023

lgtm via @arhag via DM

@heifner heifner moved this from Todo to In Progress in Team Backlog Dec 6, 2023
@heifner heifner added the OCI Work exclusive to OCI team label Dec 6, 2023
heifner added a commit that referenced this issue Dec 6, 2023
@heifner heifner moved this from In Progress to Awaiting Review in Team Backlog Dec 6, 2023
heifner added a commit that referenced this issue Dec 6, 2023
heifner added a commit that referenced this issue Dec 6, 2023
[5.0] Return error for num == 0 for bls_g1_weighted_sum, bls_g2_weighted_sum and bls_pairing
heifner added a commit that referenced this issue Dec 6, 2023
[5.0 -> main] Return error for num == 0 for bls_g1_weighted_sum, bls_g2_weighted_sum and bls_pairing
@github-project-automation github-project-automation bot moved this from Awaiting Review to Done in Team Backlog Dec 6, 2023
@heifner heifner modified the milestones: Leap v5.0.0, Leap v5.0.0-rc3 Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment