Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outputs by id failed: Request error: Wrong response code: 414 URI Too Long #2746

Closed
rentenmark opened this issue Apr 11, 2019 · 1 comment · Fixed by #2747
Closed

Outputs by id failed: Request error: Wrong response code: 414 URI Too Long #2746

rentenmark opened this issue Apr 11, 2019 · 1 comment · Fixed by #2747

Comments

@rentenmark
Copy link
Contributor

Describe the bug
during the refresh of the wallet balance, the node returns a 414 error code.

To Reproduce
It is definitely difficult to reproduce, for some reason it is transient. Re-building the wallet from seed "fixes" this problem for a while, probably until there are some number N of new incoming transactions.

I readily admit that I don't have full reproduction steps but it has something to do with the batching of outputs by id during the refresh. Thankfully, the logs that we added proved my theory that the url was too long.

Relevant Information

20190410 20:13:47.367 ERROR grin_wallet::node_clients::http - Outputs by id failed: Request error: Wrong response code: 414 URI Too Long with data Body
20190410 20:13:47.367 ERROR grin_wallet::libwallet::api - failed to refresh outputs for wallet with error : Error { inner:

Client Callback Error: Getting outputs by id: Request error: Wrong response code: 414 URI Too Long with data Body }

Desktop (please complete the following information):

  • OS: Ubuntu 16.10 running inside docker

suggested fix

Remove batching in get_outpts_by_id and add a POST parameter make the wallet POST the list of outputs to the get_outputs_by_id node endpoint.

@antiochp
Copy link
Member

Oof.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants