livepeer / livepeer/go-livepeer

livepeer_cli for Broadcaster: "Error getting status" on startup and when calling "Get node status"

Open
#2,186 1 comment 0 reactions 1 assignee View on GitHub

@emranemran is already working on this.

Since Jun 3, 2022.

area: cli good first issue hacktoberfest help wanted type: bug
Dominant language
Go
Stars
586
Forks
226
Avg merge
1d 17h
Merged PRs (30d)
19

Description

Summary

When using the livepeer_cli to configure a Broadcaster, the following message is displayed in the cli UI on a) startup, and b) calling 1. Get node status:

ERROR: logging before flag.Parse: E0116 11:52:21.005601    6268 wizard_stats.go:28] Error getting status:json: cannot unmarshal string into Go struct field OrchestratorLocalInfo.OrchestratorPoolInfos.Url of type url.URL

To Reproduce

Steps to reproduce the behavior:

  1. Run livepeer in -broadcaster mode with the following command (for completeness):
./livepeer -broadcaster \
        -network rinkeby \
        -ethUrl https://rinkeby.infura.io/v3/888a...243d \
        -pixelsPerUnit 1
  1. Observe the aforementioned error message being displayed (see screenshot)
  2. Run option 1. Get node status
  3. Observe the aforementioned error message being displayed (see screenshot)

Expected behavior

I expect the livepeer_cli to not display unnecessary error message, in order to give new Broadcasters a feeling that the software is robust and mature for their usage.

Environment

  • Ubuntu 20.04.3 LTS
  • livepeer 0.5.25

Screenshots:

On starting up the cli:

image

On calling 1. Get node status

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.