Mario Macias
Mario Macias
[According to the Type parameters proposal](https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md), it is not allowed to define type parameters in methods. This limitation prevents to define functional-like stream processing primitives, e.g.: ```go func (si *stream[IN])...
Given a body using a label from a custom type that has `string` as underlying type: ```go type Custom string type Body struct { Block struct { Name Custom `hcl:"name,label"`...
> Please check if what you want to add to `awesome-go` list meets [quality standards] **Please provide package links to:** - repo link (github.com, gitlab.com, etc): https://github.com/mariomac/gostream - pkg.go.dev: https://pkg.go.dev/github.com/mariomac/gostream...
You should probably add [dropWhile](https://docs.oracle.com/javase/9/docs/api/java/util/stream/Stream.html#dropWhile-java.util.function.Predicate-) and [takeWhile](https://docs.oracle.com/javase/9/docs/api/java/util/stream/Stream.html#takeWhile-java.util.function.Predicate-) to support ending infinite streams based on some sort of condition. It could also be a good idea to add support for "finite...
### Description Currently, the [OpenTelemetry Go Instrumentation](https://github.com/open-telemetry/opentelemetry-go-instrumentation) project contains a tool to track the offsets of struct fields across different versions of Go and third-party libraries. This tool is useful...
If any of the beyla components is stalled and you stop Beyla, it could get too much time in the `msg="exiting auto-instrumenter" component=beyla.Instrumenter` status. We should add a timeout that...
A configuration like this: ```yaml exclude_interfaces: - ens5 - lo - tunl0 - /^docker/ - /^cali/ ``` `BEYLA_NETWORK_DEDUPER=none` The reported iface is "unknown" and even if the selected direction is...
According to: https://opentelemetry.io/docs/specs/otel/common/mapping-to-non-otlp/#instrumentationscope otel.library.name is deprecated in favour of otel.scope.name
We register services on the prometheus exporter but never unregister them when a service is removed. This might cause a memory leak for some ephemeral environments (short-lived processes)