You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start a localnet with a REST client listening. Any POST request will result in:
{
"error": "http: request body too large"
}
Digging into the Go source code, I see MaxBytesReader is called. However, it's called with a max size of 0. Furthermore, even if I manually set MaxBytesReader in ReadRESTReq, I notice the constructor gets called TWICE and not only that, but the first time N is 0! It's as if the handler is being executed twice.
Why is MaxBytesReader being called twice?
Why is the 1st call being invoked with N: 0?
Note: This does not happen with the LCD tests
Oddity 2
While updating Gaia to use the latest SDK master, I noticed certain queries in the LCD tests internally had stale CLIContext values. Namely, the height.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Oddity 1
Start a localnet with a REST client listening. Any POST request will result in:
Digging into the Go source code, I see
MaxBytesReader
is called. However, it's called with a max size of 0. Furthermore, even if I manually setMaxBytesReader
inReadRESTReq
, I notice the constructor gets called TWICE and not only that, but the first timeN
is 0! It's as if the handler is being executed twice.MaxBytesReader
being called twice?N: 0
?Note: This does not happen with the LCD tests
Oddity 2
While updating Gaia to use the latest SDK master, I noticed certain queries in the LCD tests internally had stale CLIContext values. Namely, the height.
For Admin Use
The text was updated successfully, but these errors were encountered: