Search Options

Results per page
Sort
Preferred Languages
Advance

Results 181 - 190 of 341 for tracers (0.13 sec)

  1. manifests/charts/istio-control/istio-discovery/files/injection-template.yaml

        {{- end }}
        {{- with (valueOrDefault .MeshConfig.TrustDomain .Values.global.trustDomain)  }}
        - name: TRUST_DOMAIN
          value: "{{ . }}"
        {{- end }}
        {{- if and (eq .Values.global.proxy.tracer "datadog") (isset .ObjectMeta.Annotations `apm.datadoghq.com/env`) }}
        {{- range $key, $value := fromJSON (index .ObjectMeta.Annotations `apm.datadoghq.com/env`) }}
        - name: {{ $key }}
          value: "{{ $value }}"
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Fri May 10 21:01:52 UTC 2024
    - 23.8K bytes
    - Viewed (0)
  2. src/runtime/tracetime.go

    // isn't granular enough to get useful information out of a trace in
    // many cases.
    //
    // This makes absolute values of timestamp diffs smaller, and so they are
    // encoded in fewer bytes.
    //
    // The target resolution in all cases is 64 nanoseconds.
    // This is based on the fact that fundamentally the execution tracer won't emit
    // events more frequently than roughly every 200 ns or so, because that's roughly
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Wed May 22 21:17:41 UTC 2024
    - 3.3K bytes
    - Viewed (0)
  3. src/runtime/runtime1.go

    	// if any of the below debug options is != 0.
    	malloc    bool
    	inittrace int32
    	sbrk      int32
    	// traceallocfree controls whether execution traces contain
    	// detailed trace data about memory allocation. This value
    	// affects debug.malloc only if it is != 0 and the execution
    	// tracer is enabled, in which case debug.malloc will be
    	// set to "true" if it isn't already while tracing is enabled.
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Thu May 30 17:52:17 UTC 2024
    - 19.3K bytes
    - Viewed (0)
  4. platforms/core-configuration/configuration-cache/src/test/kotlin/org/gradle/internal/cc/impl/serialization/codecs/AbstractUserTypeCodecTest.kt

                encoder = encoder,
                classEncoder = DefaultClassEncoder(mock()),
                beanStateWriterLookup = DefaultBeanStateWriterLookup(),
                logger = mock(),
                tracer = null,
                problemsListener = problemHandler
            )
    
        private
        fun readContextFor(inputStream: ByteArrayInputStream, codec: Codec<Any?>) =
            DefaultReadContext(
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Sat Jun 08 11:29:30 UTC 2024
    - 7.3K bytes
    - Viewed (0)
  5. platforms/core-runtime/logging/src/integTest/groovy/org/gradle/DeprecatedUsageBuildOperationProgressIntegrationTest.groovy

            verifyAll(receivedProblem(1)) {
                fqid == 'deprecation:included-build-task'
                contextualLabel == 'Included build task has been deprecated.'
            }
        }
    
        def "collects stack traces for deprecation usages at certain limit, regardless of whether the deprecation has been encountered before for warning mode #mode"() {
            file('settings.gradle') << "rootProject.name = 'root'"
    
            51.times {
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Thu Mar 28 15:16:47 UTC 2024
    - 18.9K bytes
    - Viewed (0)
  6. staging/src/k8s.io/apiserver/plugin/pkg/audit/webhook/webhook.go

    		ctx, span := tracing.Start(context.Background(), "Call Audit Events webhook",
    			attribute.String("name", b.name),
    			attribute.Int("event-count", len(list.Items)),
    		)
    		// Only log audit webhook traces that exceed a 25ms per object limit plus a 50ms
    		// request overhead allowance. The high per object limit used here is primarily to
    		// allow enough time for the serialization/deserialization of audit events, which
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Mon Nov 07 21:13:31 UTC 2022
    - 4.5K bytes
    - Viewed (0)
  7. src/runtime/traceexp.go

    package runtime
    
    // traceExpWriter is a wrapper around trace writer that produces traceEvExperimentalBatch
    // batches. This means that the data written to the writer need not conform to the standard
    // trace format.
    type traceExpWriter struct {
    	traceWriter
    	exp traceExperiment
    }
    
    // unsafeTraceExpWriter produces a traceExpWriter that doesn't lock the trace.
    //
    // It should only be used in contexts where either:
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Wed May 08 17:47:01 UTC 2024
    - 2.4K bytes
    - Viewed (0)
  8. src/internal/trace/summary.go

    package trace
    
    import (
    	"cmp"
    	"slices"
    	"strings"
    	"time"
    )
    
    // Summary is the analysis result produced by the summarizer.
    type Summary struct {
    	Goroutines map[GoID]*GoroutineSummary
    	Tasks      map[TaskID]*UserTaskSummary
    }
    
    // GoroutineSummary contains statistics and execution details of a single goroutine.
    // (For v2 traces.)
    type GoroutineSummary struct {
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Thu May 23 01:00:11 UTC 2024
    - 20.7K bytes
    - Viewed (0)
  9. pkg/log/options.go

    				s, levelListString))
    
    		stringVar(&o.stackTraceLevels, "log_stacktrace_level", o.stackTraceLevels,
    			fmt.Sprintf("Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of "+
    				"<scope>:<level>,<scope:level>,... where scope can be one of [%s] and level can be one of %s",
    				s, levelListString))
    
    		stringVar(&o.logCallers, "log_caller", o.logCallers,
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Fri Jun 07 04:04:34 UTC 2024
    - 10.6K bytes
    - Viewed (0)
  10. doc/next/3-tools.md

    errors with a very large `CGO_LDFLAGS`.
    
    ### Trace {#trace}
    
    <!-- go.dev/issue/65316 -->
    The `trace` tool now better tolerates partially broken traces by attempting to
    recover what trace data it can. This functionality is particularly helpful when
    viewing a trace that was collected during a program crash, since the trace data
    leading up to the crash will now [be recoverable](/issue/65319) under most
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue May 28 19:06:07 UTC 2024
    - 3.4K bytes
    - Viewed (0)
Back to top