Search Results for "using"

Delve is a debugger for the Go programming language. The goal of the project is to provide a simple, full featured debugging tool for Go. Delve should be easy to invoke and easy to use. Chances are if you're using a debugger, things aren't going your way. With that in mind, Delve should stay out of your way as much as possible. Delve aims to be a very simple and powerful tool, but can be confusing if you're not used to using a source level debugger in a compiled language. This document will provide all the information you need to get started debugging your Go programs. ...

...Allows you to store large volumes of high cardinality profiling data cheaply and efficiently. FlameQL enables custom queries to select and aggregate profiles quickly and efficiently for easy analysis. Analyze application performance profiles using our suite of profiling tools. Understand usage of CPU and memory resources at any point in time and identify performance issue before your customer do. Collect, store, and analyze profiles from various external profiling tools in one central location. Link to your Open Telemetry tracing data and get request-specific or span-specific profiles to enhance other observability data like traces and logs.

...It is fast, listing bugs or opening them is a matter of milliseconds. git-bug doesn't pollute your project, no files are added in your project. git-bug integrates with your tooling, use the UI you like (CLI, terminal, web) or integrate with your existing tools through the CLI or the GraphQL API. git-bug bridges to other bug trackers. Use bridges to import and export to other trackers. An interactive terminal UI is available using the command git bug termui to browse and edit bugs.

...The errors package allows programmers to add context to the failure path in their code in a way that does not destroy the original value of the error. Wrap function returns a new error that adds context to the original error. Using errors.Wrap constructs a stack of errors, adding context to the preceding error. Depending on the nature of the error it may be necessary to reverse the operation of errors.Wrap to retrieve the original error for inspection. Any error value which implements this interface can be inspected by errors.Cause. errors.Cause will recursively retrieve the topmost error which does not implement causer, which is assumed to be the original cause.