-
Notifications
You must be signed in to change notification settings - Fork 214
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
[Merged by Bors] - v2alpha1 malfeasance API #6353
Conversation
5b88a9c
to
ad327df
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6353 +/- ##
=========================================
- Coverage 81.7% 81.6% -0.2%
=========================================
Files 312 313 +1
Lines 34657 34937 +280
=========================================
+ Hits 28335 28511 +176
- Misses 4486 4581 +95
- Partials 1836 1845 +9 ☔ View full report in Codecov by Sentry. |
bors merge |
## Motivation This implements the malfeasance API for v2alpha1.
Canceled. |
bors merge |
## Motivation This implements the malfeasance API for v2alpha1.
Build failed: |
bors merge |
## Motivation This implements the malfeasance API for v2alpha1.
Pull request successfully merged into develop. Build succeeded:
|
Motivation
This implements the malfeasance API for v2alpha1.
Description
For every malfeasance proof the API returns:
Additionally I updated events to not have
wire.MalfeasanceProof
as part of the event any more but instead only the raw bytes of the proof - listeners of events in general should only care about which identities are marked as malicious and not why.Test Plan
Added test for new API and updated tests of existing handlers.
Tests in
grpcserver/v2alpha1
where sharing setup code between them which caused tests to get stuck if they are executed in a different order. I updated the tests to all setup their environment individually to avoid this.TODO