Skip to content
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

Return statuses on duties #5069

Merged

Conversation

tzapu
Copy link
Contributor

@tzapu tzapu commented Mar 11, 2020

Resolves #5002

Description

  • adds metrics for validator key statuses
  • returns correct status on GetDuties for DEPOSITED as well
  • updated pkey to pubkey on all metrics (suggested by @rauljordan)

@prestonvanloon
Copy link
Member

Tests failing. Please fix.

@codecov
Copy link

codecov bot commented Mar 12, 2020

Codecov Report

Merging #5069 into master will increase coverage by 38.37%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #5069       +/-   ##
==========================================
+ Coverage    6.42%   44.8%   +38.37%     
==========================================
  Files         101     218      +117     
  Lines        7528   17387     +9859     
==========================================
+ Hits          484    7790     +7306     
- Misses       6982    8220     +1238     
- Partials       62    1377     +1315

@tzapu
Copy link
Contributor Author

tzapu commented Mar 12, 2020

i think i sorted it... lemme know if there's anything else
impressive test suite btw 👑

this can't be right tho... can it?
image

@rauljordan
Copy link
Contributor

Thanks @tzapu ! Yeah codecov is pretty inaccurate so good to ignore for now

@prylabs-bulldozer prylabs-bulldozer bot merged commit 0704ba6 into prysmaticlabs:master Mar 12, 2020
@tzapu tzapu deleted the return-statuses-on-duties branch March 13, 2020 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

validator node not providing feedback when a secondary key's status changes
4 participants