I've been trying to root cause an OOM condition. My process is running
within a cgroup with a 4gb limit. Occasionally that limit gets hit. I
added a cgroup listener to watch for memory usage and create a pprof and
core dump.
The pprof shows just a few hundred megs of "in-use" memory, however
On Saturday, January 29, 2022 at 5:12:48 AM UTC+11 kimiyas...@gmail.com
wrote:
> Hi
>
> i have a struct event and inner that i have struct RequestRecord
> *type RequestRecord struct {*
> * ID string `json:"id"`*
> * Addr string `json:"addr"`*
> * Host string `json:"host"`*
> * Method string `
On Fri, Jan 28, 2022 at 6:44 AM frankre...@gmail.com
wrote:
>
> https://github.com/golang/go/issues/49741
>
> x/net/http2: http.Server.WriteTimeout does not fire if the http2 stream's
> window is out of space. #49741
>
> The 1.17 back port issue:
> x/net/http2: http.Server.WriteTimeout does not f
It's very well-explained and the code's easy to read. And you can build on
it. I've been able to modify his code to my language spec, use syntactic
whitespace instead of braces, utf8 instead of ASCII, my idea of how
continuations should work, line numbers in error messages, the ability to
defi
Hi
i have a struct event and inner that i have struct RequestRecord
*type RequestRecord struct {*
* ID string `json:"id"`*
* Addr string `json:"addr"`*
* Host string `json:"host"`*
* Method string `json:"method"`*
* UserAgent string `json:"useragent"`*
*}*
*type event struct {*
* ID string `json
> 2) Long variable names.
Where I work (not in Go), writing comments is frowned upon. That includes
"docblock" style comments. If a function needs to be documented, it means
the implementation is too complex and must be broken apart to reduce
cyclomatic or whatever perceived complexity. Also un
https://github.com/golang/go/issues/49741
x/net/http2: http.Server.WriteTimeout does not fire if the http2 stream's
window is out of space. #49741
The 1.17 back port issue:
x/net/http2: http.Server.WriteTimeout does not fire if the http2 stream's
window is out of space. [1.17 backport] #49921
On Thursday, January 27, 2022 at 10:53:52 PM UTC+1 Ian Lance Taylor wrote:
> On Thu, Jan 27, 2022 at 1:38 PM Manlio Perillo
> wrote:
> > > > On Thursday, January 27, 2022 at 11:42:19 AM UTC+1 Manlio Perillo
> wrote:
> > > [...]
> > > > Here is an alternate implementation:
> > > > https://go
