-
Notifications
You must be signed in to change notification settings - Fork 2.1k
simplify get_seed_for_proof() #20299
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
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
get_seed_for_proof expects at least two sub epochs, it will throw without this.
we cannot get a sees if we dont have 2 finished sub epochs at least
we cannot change how the seed is chosen since it is verified by the verifier so we can change this without being incompatible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what you mean by this comment. It is possible to call this function with a height that only yields a single summary height. The existing behavior is to throw a
KeyErrorexception in this case. It took some investigation to understand what that meant. I would think this is an improvement, as a clearer error is printed to the log. I'm pretty confident returningNonehas essentially the same effect as the exception, we fail to respond to this weight proof request either way.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this error should be thrown from inside get_seed_for_proof
i missed that this is supposed to be equivalent to the current code (i think its less readable but maybe im just familiar with the old) i always prefer not fixing something thats not broken especially critical code, we can add the error there instead of the assert thats fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it's a good point that it's always risky to change code that works. I think this especially applies to
get_seed_for_proof(). I'll propose a less intrusive change to that function.Regarding the error reporting here. Is this case materially different from the other failure cases here, to warrant an exception instead of returning
None?For example, if
self.blockchain.try_block_record(tip)orself._get_recent_chain(tip_rec.height)returnsNone.