Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3275 +/- ##
===================================================
- Coverage 32.16679% 30.41730% -1.74949%
===================================================
Files 147 148 +1
Lines 41033 43518 +2485
===================================================
+ Hits 13199 13237 +38
- Misses 27058 29505 +2447
Partials 776 776
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
98fa9ab to
8dc634f
Compare
| confirm = w.readStringYesOrNo() | ||
| } | ||
|
|
||
| fmt.Printf("Do you want to provide a reason for your vote? (y/n) -") |
There was a problem hiding this comment.
Would be awesome to display these in the dashboard at some point!
There was a problem hiding this comment.
Mike will be adding it to his vote tracker. At the moment it is just me and Titan setting the reason, but with this PR we might see a lot more Orchestrators add a reason to their vote.
86714fa to
ad52dce
Compare
|
LGTM @rickstaa feel free to merge. |
@leszko thanks. I now also tested the code without a reason.
|
This commit allows orchestrators to vote on active treasury proposal directly from the go-livepeer CLI.
This commit ensures that the contract bindings are up to date with the latest version of the livepeer/protocol repository.
This commit renames the internal reference to the LivepeerGovernor contract and improves the proposalVote handler data type parsing behavoir.
This commit makes the CLI description for proposal voting more specific to prevent confusion. Co-authored-by: Victor Elias <victor@livepeer.org>
4a0fffc to
6caa873
Compare
What does this pull request do? Explain your changes. (required)
This pull request gives orchestrators the ability to vote on active treasury proposal directly from the go-livepeer CLI.
Specific updates (required)
voteOnProposalhandler on the server.go generate client.go. Can you check if these really need to be updated or that my setup is incorrect.How did you test each of these updates (required)
I wrote tests and tested the command line argument with a non-orchestrator wallet since we currently don't have a testnet. @victorges, @leszko if you reviewed this I can test with my actual wallet.
Does this pull request close any open issues?
Checklist:
makeruns successfully./test.shpass