Being configurable would be the easiest way. I am asking how I can read this value at runtime init time.
-- Michele Sciabarra [email protected] ----- Original message ----- From: Carlos Santana <[email protected]> To: [email protected] Subject: Re: How to pass size the max size of the request to the runtime? Date: Tue, 11 Sep 2018 09:08:01 -0400 If it can be dynamic and detected from content-length that would be good if not then set it to higher value than 1MB like 5MB (this is value I have heard some users mentioned that want to use when talking about large payload inputs) Also in addition what about making configurable?, meaning can be override the default using a environment variable that can be redefined in the Dockerfile when building/extending the image or in docker cli during container creation. -- Carlos On Tue, Sep 11, 2018 at 9:02 AM Rodric Rabbah <[email protected]> wrote: > The http post will have a content length is that useful? > > -r > > > On Sep 10, 2018, at 7:45 AM, Michele Sciabarra <[email protected]> > wrote: > > > > Hello, I am in the process of running the mandatory tests against the Go > Runtime. > > In the process, I fixed a lot of bugs, because those tests revealed a > number of details about encoding, env variables and other things that were > not obvious to me in the first place. > > > > Now I have a problem: I am trying to pass the test that tried to send a > one-megabyte big request to the runtime. > > Currently, it does not work because I discovered the "scan" buffer has > in Golang a fixed size of 64k. > > > > Of course, I can increase it but I need to know how big it must be. I > know that you can set some parameters at OpenWhisk level but I am not aware > how a runtime can know those parameters. Most notably I need to be able to > read the maximum size of the requests because I need to allocate a buffer > at init time. Any hints? > > > > > > -- > > Michele Sciabarra > > [email protected] >
