Austin Drenski

Draft: Update types to parse with ReadOnlySpan<char>

2

_Work in progress:_ ## `NpgsqlRange` ``` BenchmarkDotNet=v0.10.14, OS=Windows 10.0.17134 Intel Core i7-6650U CPU 2.20GHz (Skylake), 1 CPU, 4 logical and 2 physical cores Frequency=2156252 Hz, Resolution=463.7677 ns, Timer=TSC .NET Core...

Add support to record errors from lambda handlers

4

Currently, `otellambda` doesn't update the instrumentation-provided span based on the result of the wrapped handler. I was surprised by this, as most of my OTel instrumentation work involves [open-telemetry/opentelemetry-dotnet](https://github.com/open-telemetry/opentelemetry-dotnet), so...

Fixes: #1084, #2086, docker/compose-ecs#19, docker/compose-ecs#20 ___ I'm aware that in light of the impending EOL per #2258, that this contribution will very likely not be accepted, however, I'm still opening...

Update docs with bit array examples

1

See npgsql/npgsql#2269

[FEATURE] flagd should use standard OTel SDK env vars

5

### Requirements ## Request Replace `--otel-collector-uri`/`FLAGD_OTEL_COLLECTOR_URI` and `--metrics-exporter`/`FLAGD_METRICS_EXPORTER` with well-known OTel SDK configuration environment variables. - https://opentelemetry.io/docs/concepts/sdk-configuration/ - https://opentelemetry.io/docs/concepts/sdk-configuration/general-sdk-configuration/ - https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/ ```diff services: flagd: command: - start - --debug -...

refactor: Use standard OTel SDK env vars

6

- https://opentelemetry.io/docs/concepts/sdk-configuration/ - https://opentelemetry.io/docs/concepts/sdk-configuration/general-sdk-configuration/ - https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/ Closes: #1141 ___ > [!NOTE] > > _Fully aware that this neither sufficient nor suitable as is, but opening as a companion to #1141...

Fixes: #17 See: 48016d5c35193c9e253399d90c07a9e0bef6fbcc

Opening to track resolution of docker/compose-cli#1084 and docker/compose-cli#2086 originally reported by @theirix and @jared-hess, respectively. See: docker/compose-cli#1084, docker/compose-cli#2086, docker/compose-cli#2269