-
-
Notifications
You must be signed in to change notification settings - Fork 660
undo ancient hack to resolve #35017 #35018
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
Conversation
I tried but couldn't catch the bug that really causes the failure. Can you explain? |
What happens here is that sometimes elliptic-curve points are constructed which are "officially" defined over (say) a finite field, but the coordinates are represented as integers. This breaks some assumptions I made writing code like this: The |
Isn't it |
Here in the traceback:
|
Okay. Now I understand the situation. Thanks. Let's wait for the checks for sanity. |
Codecov ReportBase: 88.59% // Head: 88.59% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #35018 +/- ##
========================================
Coverage 88.59% 88.59%
========================================
Files 2136 2136
Lines 396141 396142 +1
========================================
+ Hits 350977 350979 +2
+ Misses 45164 45163 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
The comment in the code says that these coordinates must be integers, but it appears that setting them to base-ring elements works now. This fixes the underlying cause of the random failure. (Resolves #35017.)