Long Excerpt results in Failed Publish
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 21
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
DESCRIPTION:
If the user submits a new or edited post with a long Excerpt, it will fail to publish to LBRY with the following error in the 'lbrynet' console:
"lbry.wallet.rpc.jsonrpc.RPCError: (1, 'the transaction was rejected by network rules.\n\nbad-txns-claimscriptsize-toolarge (code 16)"
REPRO STEPS:
- Log into self-hosted Wordpress site w/ LBRYPress Plugin
- Create a New Post
- Enter 10000 characters into the Excerpt
- Publish the Post
Results: Post does not publish on LBRY
Expected: Post publishes on LBRY, or user receives an error in the Wordpress UI
ENVIRONMENT:
Ubuntu 18.04.4
WordPress 5.3.3
PHP 7.2.24
LBRYPress 0.0.1
Lodestar Theme 1.0.8
CALLSTACK:
2020-05-24 16:42:08,690 ERROR lbry.extras.daemon.daemon:706: error handling api request
Traceback (most recent call last):
File "lbry/extras/daemon/daemon.py", line 698, in _process_rpc_call
File "lbry/extras/daemon/daemon.py", line 3039, in jsonrpc_publish
File "lbry/extras/daemon/daemon.py", line 3482, in jsonrpc_stream_update
File "lbry/extras/daemon/daemon.py", line 5240, in broadcast_or_release
File "lbry/wallet/manager.py", line 301, in broadcast_or_release
File "lbry/wallet/network.py", line 83, in send_request
File "lbry/wallet/network.py", line 73, in send_request
File "lbry/wallet/rpc/session.py", line 479, in send_request
IMAGES:

LBRY ADDRESS:
bZSqrVdpxt5KJdn2eGMUzT9Jn3gEiRet7b
mail@cahlen.org
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the 10,000-character Excerpt case in a self-hosted WordPress site with the LBRYPress plugin, then inspect the publish flow alongside the lbrynet console output and the listed RPC call stack. Done means the post either publishes successfully or the WordPress UI reports the failure instead of silently failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100