-
Notifications
You must be signed in to change notification settings - Fork 2k
various typing fixes #15899
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
various typing fixes #15899
Conversation
This is a benchmark. We probably don't run it on CI, but even if we did, we don't instrument benchmarks for coverage |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
24e1212
to
c3a5ab0
Compare
This comment was marked as resolved.
This comment was marked as resolved.
cf9c319
to
82853e1
Compare
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 excited about adding type stubs here for other packages, but I'm also not driving the future of these libs. The asserts in the runtime code aren't great, but are also in keeping with our practices.
Other than above and my couple inline comments I'm ok with this. Someone familiar with the actual code changes should review them specifically.
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.
Looks good
|
Pull Request Test Coverage Report for Build 5890253647
💛 - Coveralls |
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.
lgtm
This PR adds type stubs for
blspy
and addresses mypy errors that resulted from it.There are 3 lines missing coverage:
This is a trivially correct change (I think). It's encoding an invariant we have in FullBlock as an
assert
.This function seems simple to break out and unit test, which we should do in the future.
This is a typo in the DID recovery code. It should have a test. Matt reviewed the change and said it looks good. I think it's a fairly trivially correct change.
We don't instrument benchmarks for coverage. And we probably don't even run this benchmark in CI, since this was another trivial typo.