Chia-Network / Chia-Network/pool-reference
[Error] Request Entity Too Large
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 428
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
I got an error below in testnet, 1.2.3.
ERROR:root:Unexpected error in collect_pool_rewards_loop: 413, message='Request Entity Too Large', url=URL('https://localhost:8555/push_tx') Traceback (most recent call last):
File "/home/chia/testnet/pool-reference/pool/pool.py", line 332, in collect_pool_rewards_loop
push_tx_response: Dict = await self.node_rpc_client.push_tx(spend_bundle)
File "/home/chia/testnet/pool-reference/venv/lib/python3.8/site-packages/chia/rpc/full_node_rpc_client.py", line 162, in push_tx
return await self.fetch("push_tx", {"spend_bundle": spend_bundle.to_json_dict()})
File "/home/chia/testnet/pool-reference/venv/lib/python3.8/site-packages/chia/rpc/rpc_client.py", line 42, in fetch
response.raise_for_status()
File "/home/chia/testnet/pool-reference/venv/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 1000, in raise_for_status
raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 413, message='Request Entity Too Large', url=URL('https://localhost:8555/push_tx')
I think this is because my pool server has offline long time for about 4 days.
Does the HTTP server need to fix this problem?
I think it is related to the upload size.
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
Start with pool/pool.py around line 332 and trace the push_tx call through the Chia full-node RPC client to the /push_tx endpoint. Reproduce the 413 response using the reported four-day offline scenario, then determine which request-size handling component is responsible. Done means the reward collection request completes successfully or the responsible HTTP limit is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100