Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
This package provides a reporter for the go-metrics library which posts the metrics to the Prometheus client registry and just updates the registry.
sigv4 provides a http.RoundTripper that will sign requests using Amazon's Signature Verification V4 signing procedure, using credentials from the default AWS credential chain.
The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integrations such as email, PagerDuty, OpsGenie, or many other mechanisms thanks to the webhook receiver. It also takes care of silencing and inhibition of alerts.
This package implements Internet Control Message Protocol echo (ping) functionality.
The procfs Go package provides functions to retrieve system, kernel, and process metrics from the /proc pseudo file system.
This package provides data model artifacts for Prometheus.
This package implements a Prometheus monitoring for your gRPC Go servers and clients.
Prometheus monitoring and https://godoc.org/golang.org/x/net/trace# tracing wrappers net.Conn, both inbound (@codenet.Listener) and outbound (@codenet.Dialer).
This package provides Go libraries that are shared across Prometheus components.
config- common configuration structuresexpfmt- decoding and encoding for the exposition formatmodel- shared data structurespromslog- a logging wrapper around log/slogroute- a routing wrapper around httprouter using context.Contextserver- common serversversionversion information and metrics
python-pure-protobuf takes advantage of the standard dataclasses module to define message types. Protocol buffers are a language-neutral, platform-neutral extensible mechanism for serializing structured data.
Protozero is a minimalistic protocol buffer decoder and encoder in C++. The developer using protozero has to manually translate the .proto description into code.
Protocol buffers are a language-neutral, platform-neutral extensible mechanism for serializing structured data.
fstrm is an optimised implementation of Frame Streams as a C library and several tools built on top of it.
Frame Streams is a light-weight, binary-clean protocol that allows for the transport of arbitrarily-encoded data payload sequences with minimal framing overhead---just four bytes per data frame. It does not specify an encoding format for these data frames and can be used with any data serialisation format that produces byte sequences, such as Protocol Buffers, XML, JSON, MessagePack, YAML, etc.
Frame Streams can be used either as a streaming transport over a reliable byte stream socket (TCP sockets, TLS connections, AF_UNIX sockets, etc.) for data in motion, or as a file format for data at rest.
Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats.
Protobuf is an implementation of Google's Protocol Buffers in pure Ruby.
Protocol buffers are a language-neutral, platform-neutral extensible mechanism for serializing structured data.
This Python package provide tools to generate Mypy stubs from protobuf specification files.
Nanopb is a small code-size Protocol Buffers implementation in ansi C. It is especially suitable for use in microcontrollers, but fits any memory-restricted system.
This is a wrapper around protocol buffers. Protocol buffers is a specification format for APIs, such as those inside Google. This library provides protocol buffer message classes and objects that largely behave like native Python types.
Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats.
Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats.
Protocol Buffers are a way of encoding structured data in an efficient yet extensible format. Google uses Protocol Buffers for almost all of its internal RPC protocols and file formats.
Nanopb is a small code-size Protocol Buffers implementation in ansi C. It is especially suitable for use in microcontrollers, but fits any memory-restricted system.
Protocol buffers are a language-neutral, platform-neutral extensible mechanism for serializing structured data.