Kaoru Kohashigawa

Ah very nice, I need to familiarize myself with the `Events` API. I'll take a gander at your PR: https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/342 -- If you have any other resources please send them...

Sorry I fat-fingered the wrong button 😞 --- hey @arielvalentin I tried using `Rack::Events` and discovered we're missing some labels. Let me explain... The way I've set up our middleware...

A potentially hacky workaround is to add a `pre-command` hook that will remove all orphaned containers: ```bash docker ps -aq | xargs docker rm -f ```

One use case I would love to support while using [Pulumi Kubernetes](https://github.com/pulumi/pulumi-kubernetes). GKE Autopilot pods are limited to `10Gi` disk space. I mistakenly configured a deployment to have containers with...

I got around this by passing the `name` as the `type`. I.E: ```ts class VPC extends ComponentResource { constructor(name: string, opts: ComponentResourceOptions = {}) { super(`VPCComponent/${name}`, name, undefined, opts) }...

> we don't accept on the socket when the thread pool is 100% full/busy. Ah -- so what causes this gauge to be non-zero then?