lbryio / lbryio/lbry-sdk

cli help output cut off / new lines not showing

Open
#2,052 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
Python
Stars
7.2k
Forks
493
PR merge metrics
No merged PRs in 30d

Description

The Issue

In account sync, the text after a sync hash and is cut off. On the 2nd example, the new lines are not working and show \n instead. This may be an issue in other commands as well.

C:\Users\thoma\Desktop>lbrynet sync --help
Usage:  lbrynet sync COMMAND ...

positional arguments:
  COMMAND
    apply  Apply incoming synchronization data, if provided, and then produce
           a sync hash and
    hash   Deterministic hash of the wallet.

Options:
  --help   Show this help message and exit.

Run 'lbrynet sync COMMAND --help' for more information on a command.

C:\Users\thoma\Desktop>lbrynet publish --name=test --bid=1 --file_path=Atom.lnk
"Invalid value for 'bid': \nDecimal inputs require a value in the ones place and in the tenths place\nseparated by a period. The value provided, '1', is not of the correct\nformat.\n\nThe following are examples of valid decimal inputs:\n\n1.0\n0.001\n2.34500\n4534.4\n2323434.0000\n\nThe following are NOT valid:\n\n83\n.456\n123.\n"

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

Internal Use

Acceptance Criteria
Definition of Done
  • Tested against acceptance criteria
  • Tested against the assumptions of user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed

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.

Research direction

Reproduce the issue with the shown lbrynet sync --help and lbrynet publish --name=test --bid=1 --file_path=Atom.lnk commands, then trace the CLI help and error-output formatting. Done means the full sync help text is displayed and the decimal error uses actual new lines instead of literal \n sequences.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.