-
Notifications
You must be signed in to change notification settings - Fork 25
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
Shuffle verification #1255
Shuffle verification #1255
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1255 +/- ##
========================================
Coverage 92.29% 92.30%
========================================
Files 200 201 +1
Lines 31577 31784 +207
========================================
+ Hits 29143 29337 +194
- Misses 2434 2447 +13 ☔ View full report in Codecov by Sentry. |
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.
good stuff, I think we should definitely write a test to validate malicious behavior (hopefully the existing framework makes it easy)
} | ||
|
||
#[cfg(all(test, unit_test))] | ||
mod tests { |
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.
is there anything that prevents us from adding a test that ensures cheaters are caught?
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.
builds on top of #1253, #1249 and #1246.
We should first merge those before reviewing this PR.