s 'Foo', 'fooBar', 'futils.Oboe', 'github.com/foo/bar.Baz'. Results are limited to 100 symbols. /debug/pprof/ /debug/pprof/

Set debug=1 as a query parameter to export in legacy text format


Types of profiles available: Identifiers, such as variable and package names, follow certain rules. See the following links for details: - https://go.dev/doc/effective_go#package-names - https://go.dev/doc/effective_go#mixed-caps - https://go.dev/wiki/CodeReviewComments#initialisms - https://go.dev/wiki/CodeReviewComments#variable-names (Or (CallExpr fn@(Or (Symbol "fmt.Print") (Symbol "fmt.Sprint") (Symbol "fmt.Println") (Symbol "fmt.Sprintln")) [(CallExpr (Symbol "fmt.Sprintf") f:_)]) (CallExpr fn@(Or (Symbol "fmt.Fprint") (Symbol "fmt.Fprintln")) [_ (CallExpr (Symbol "fmt.Sprintf") f:_)]))The \'encoding/binary\' package can only serialize types with known sizes. This precludes the use of the \'int\' and \'uint\' types, as their sizes differ on different architectures. Furthermore, it doesn't support serializing maps, channels, strings, or functions. Before Go 1.8, \'bool\' wasn't supported, either. Functions in the \'math/rand\' package that accept upper limits, such as \'Intn\', generate random numbers in the half-open interval [0,n). In other words, the generated numbers will be \'>= 0\' and \'< n\' – they don't include \'n\'. \'rand.Intn(1)\' therefore doesn't generate \'0\' or \'1\', it always generates \'0\'.Yoda conditions are conditions of the kind \"if 42 == x\", where the literal is on the left side of the comparison. These are a common idiom in languages in which assignment is an expression, to avoid bugs of the kind \"if (x = 42)\". In Go, which doesn't allow for this kind of bug, we prefer the more idiomatic \"if x == 42\".On ARM, x86-32, and 32-bit MIPS, it is the caller's responsibility to arrange for 64-bit alignment of 64-bit words accessed atomically. The first word in a variable or in an allocated struct, array, or slice can be relied upon to be 64-bit aligned. You can use the structlayout tool to inspect the alignment of fields in a struct.\'bytes.Buffer\' has both a \'String\' and a \'Bytes\' method. It is almost never necessary to use \'string(buf.Bytes())\' or \'[]byte(buf.String())\' – simply use the other method. The only exception to this are map lookups. Due to a compiler optimization, \'m[string(buf.Bytes())]\' is more efficient than \'m[buf.String()]\'. {{define "title"}}Cache {{.ID}}{{end}} {{define "body"}}

memoize.Store entries

File stats

{{- $stats := .FileStats -}} Total: {{$stats.Total}}
Largest: {{$stats.Largest}}
Errors: {{$stats.Errs}}

{{end}} {{define "title"}}Client {{.Session.ID}}{{end}} {{define "body"}} Using session: {{template "sessionlink" .Session.ID}}
{{if .DebugAddress}}Debug this client at: {{localAddress .DebugAddress}}
{{end}} Logfile: {{.Logfile}}
Gopls Path: {{.GoplsPath}}
{{end}} ATTENTION: Please answer these questions BEFORE submitting your issue. Thanks! #### What did you do? If possible, provide a recipe for reproducing the error. A complete runnable program is good. A link on play.golang.org is better. A failing unit test is the best. #### What did you expect to see? #### What did you see instead? Ranging over a string will yield byte offsets and runes. If the offset isn't used, this is functionally equivalent to converting the string to a slice of runes and ranging over that. Ranging directly over the string will be more performant, however, as it avoids allocating a new slice, the size of which depends on the length of the string.A \'net.IP\' stores an IPv4 or IPv6 address as a slice of bytes. The length of the slice for an IPv4 address, however, can be either 4 or 16 bytes long, using different ways of representing IPv4 addresses. In order to correctly compare two \'net.IP\'s, the \'net.IP.Equal\' method should be used, as it takes both representations into account.\'(*net/url.URL).Query\' parses the current value of \'net/url.URL.RawQuery\' and returns it as a map of type \'net/url.Values\'. Subsequent changes to this map will not affect the URL unless the map gets encoded and assigned to the URL's \'RawQuery\'. As a consequence, the following code pattern is an expensive no-op: \'u.Query().Add(key, value)\'.InvalidDotDotDotUncalledBuiltinInvalidAppendInvalidCapInvalidCloseInvalidCopyInvalidComplexInvalidDeleteInvalidImagInvalidLenSwappedMakeArgsInvalidMakeInvalidRealInvalidAssertImpossibleAssertInvalidConversionInvalidUntypedConversionBadOffsetofSyntaxInvalidOffsetofUnusedExprUnusedVarMissingReturnWrongResultCountOutOfScopeResultInvalidCondInvalidPostDeclstateTextstateTagstateAttrNamestateAfterNamestateBeforeValuestateHTMLCmtstateRCDATAstateAttrstateURLstateSrcsetstateJSstateJSDqStrstateJSSqStrstateJSTmplLitstateJSRegexpstateJSBlockCmtstateJSLineCmtstateJSHTMLOpenCmtstateJSHTMLCloseCmtstateCSSstateCSSDqStrstateCSSSqStrstateCSSDqURLstateCSSSqURLstateCSSURLstateCSSBlockCmtstateCSSLineCmtstateErrorstateDeadHTTP has a tremendous number of status codes. While some of those are well known (200, 400, 404, 500), most of them are not. The \'net/http\' package provides constants for all status codes that are part of the various specifications. It is recommended to use these constants instead of hard-coding magic numbers, to vastly improve the readability of your code. \'sort.Float64Slice\', \'sort.IntSlice\', and \'sort.StringSlice\' are types, not functions. Doing \'x = sort.StringSlice(x)\' does nothing, especially not sort any values. The correct usage is \'sort.Sort(sort.StringSlice(x))\' or \'sort.StringSlice(x).Sort()\', but there are more convenient helpers, namely \'sort.Float64s\', \'sort.Ints\', and \'sort.Strings\'. The \'encoding/json\' and \'encoding/xml\' packages only operate on exported fields in structs, not unexported ones. It is usually an error to try to (un)marshal structs that only consist of unexported fields. This check will not flag calls involving types that define custom marshaling behavior, e.g. via \'MarshalJSON\' methods. It will also not flag empty structs.detect some violations of the cgo pointer passing rules Check for invalid cgo pointer passing. This looks for code that uses cgo to call C code passing values whose types are almost always invalid according to the cgo pointer sharing rules. Specifically, it warns about attempts to pass a Go chan, map, func, or slice to C, either directly, or via a pointer, array, or struct.Test executables (and in turn \"go test\") exit with a non-zero status code if any tests failed. When specifying your own \'TestMain\' function, it is your responsibility to arrange for this, by calling \'os.Exit\' with the correct code. The correct code is returned by \'(*testing.M).Run\', so the usual way of implementing \'TestMain\' is to end it with \'os.Exit(m.Run())\'. A duration must be as "number", without any spaces. Valid units are: ns nanoseconds (billionth of a second) us, µs microseconds (millionth of a second) ms milliseconds (thousands of a second) s seconds m minutes h hours You can combine multiple units; for example "5m10s" for 5 minutes and 10 seconds. The \'os/signal\' package uses non-blocking channel sends when delivering signals. If the receiving end of the channel isn't ready and the channel is either unbuffered or full, the signal will be dropped. To avoid missing signals, the channel should be buffered and of the appropriate size. For a channel used for notification of just one signal value, a buffer of size 1 is sufficient.{{if and .StmtOK (eq (.TypeName .Type) "error") -}} {{- $errName := (or (and .IsIdent .X) "err") -}} if {{if not .IsIdent}}err := {{.X}}; {{end}}{{$errName}} != nil
CountProfile