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

feat: returns error on invalid proof range in buildRangeProof #182

Merged
merged 15 commits into from
Apr 27, 2023

Conversation

staheri14
Copy link
Contributor

@staheri14 staheri14 commented Apr 25, 2023

Overview

Closes #142

Checklist

  • New and updated code has appropriate documentation
  • New and updated code has new and/or updated testing
  • Required CI checks are passing
  • Visual proof for any user facing features like CLI or documentation updates
  • Linked issues closed with keywords

@staheri14 staheri14 self-assigned this Apr 25, 2023
@staheri14 staheri14 added the enhancement New feature or request label Apr 25, 2023
@staheri14 staheri14 marked this pull request as ready for review April 25, 2023 21:19
@staheri14 staheri14 requested review from rootulp, evan-forbes, liamsi and cmwaters and removed request for rootulp April 25, 2023 21:20
@codecov
Copy link

codecov bot commented Apr 25, 2023

Codecov Report

Merging #182 (d491b52) into master (21c6427) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #182      +/-   ##
==========================================
+ Coverage   94.09%   94.14%   +0.05%     
==========================================
  Files           5        5              
  Lines         542      547       +5     
==========================================
+ Hits          510      515       +5     
  Misses         18       18              
  Partials       14       14              
Impacted Files Coverage Δ
nmt.go 98.00% <100.00%> (+0.05%) ⬆️

cmwaters
cmwaters previously approved these changes Apr 26, 2023
Copy link

@cmwaters cmwaters left a comment

Choose a reason for hiding this comment

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

LGTM. I'm assuming that the range includes start and excludes end right?

nmt.go Outdated Show resolved Hide resolved
evan-forbes
evan-forbes previously approved these changes Apr 26, 2023
Copy link
Member

@evan-forbes evan-forbes left a comment

Choose a reason for hiding this comment

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

+1 to Callum's comment, otherwise LGTM!

@staheri14 staheri14 dismissed stale reviews from evan-forbes and cmwaters via fcd3cd0 April 26, 2023 16:45
@staheri14
Copy link
Contributor Author

LGTM. I'm assuming that the range includes start and excludes end right?

Yes, you are right, I added a comment to the function to make it more clear, please see fcd3cd0

@staheri14 staheri14 requested a review from cmwaters April 26, 2023 16:47
cmwaters
cmwaters previously approved these changes Apr 26, 2023
rootulp
rootulp previously approved these changes Apr 26, 2023
nmt.go Outdated Show resolved Hide resolved
@staheri14 staheri14 dismissed stale reviews from rootulp and cmwaters via d491b52 April 26, 2023 20:14
@staheri14 staheri14 merged commit f05092f into master Apr 27, 2023
@staheri14 staheri14 deleted the verifies-proof-range branch April 27, 2023 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

buildRangeProof can panic upon invalid input range
4 participants