Aaron Jacobs
Aaron Jacobs
#10 added fairly sophisticated control of acknowledgements, but the documentation isn't very discoverable and these techniques are too specialised to put in the README. It makes sense to add a...
This is possible via the underlying `librabbitmq` (see [example](https://github.com/alanxz/rabbitmq-c/blob/master/examples/amqp_ssl_connect.c)) but has not been implemented in `longears`.
Exemplars are an optional feature of the OpenMetrics standard that attaches metadata about an individual sample to a histogram bucket, including its value, optional labels, and an optional timestamp: ```...
The existing Python client can serve as the reference implementation.
See: https://github.com/prometheus/client_python/blob/5b0a476489fc6a26c177683b539142c91005de06/prometheus_client/utils.py#L8 This is already (mostly) done for the histogram `le` labels, but applies to all metric formatting generally.
Shiny exposes various "hooks" to run user code when various events occur -- `onFlush()`, `onSessionEnded()`, and so on. One notable omission from the existing hooks is the ability to capture...
**Is your feature request related to a problem? Please describe.** Currently, `devtools::test()` is tied to the **testthat** package, which is sensible enough. However, there are more than a hundred CRAN...
As proposed in #284: the new [OpenMetrics](https://openmetrics.io/) standard is the next-gen format for consuming and emitting Prometheus metrics, and has been supported by Prometheus itself for a few years now....
Retrying requests is a good way to make code robust against transient failures in the upstream API. However, even with exponential backoff, it still faces a fundamental challenge when the...