livepeer / livepeer/go-livepeer
Trying to get started, but getting error message. Make the error message more understandable.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
I am trying to do the first part of becoming an orchestrator, but am getting the following error message about insufficient funds: Error applying configuration: insufficient funds for gas * price + value.
To Reproduce
Steps to reproduce the behavior:
- Run
livepeer_cli. - Select
13. Set orchestrator configby typing '13' and pressing enter. - Get the error message:
Error applying configuration: insufficient funds for gas * price + value.
Expected behavior
I would like it to give me (and other users) clear instructions on exactly how much by balance is short by (how much extra eth I need to deposit), and then potentially even tell me exactly where to send the funds.
Additional instructions outlining that having funds in the wallet is a critical step in the Transcoding Setup Guide would be very helpful. In hindsight, it's quite obvious, but I don't doubt that I'm not the only user who's wasted time on "obvious" steps that aren't detailed in the guide.
Do the funds need to be in LPT, Eth, WEI, etc.?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through the livepeer_cli “Set orchestrator config” entry point and review the Transcoding Setup Guide section linked in the report. Clarify whether the insufficient-funds message should explain the shortfall and required currency, and update the error guidance and setup documentation so users know how to fund the wallet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100