Marc Bachmann

The dependencies got updated on the branch `main`: https://github.com/pragmaticivan/nestjs-otel/commit/c2f8b7b9fbe116953521fb6b5d7f4648d09d7712#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R42

> I personally prefer ordered tests, so I think there should be some language in the specification that says that producers SHOULD provide a means of producing ordered test results....

> Same problem here. The node instance ID is set by default to the container IP of the exporter, not the hostname of the actual host. It's confusing and weird....

Yeah, that would be a breaking change. What about making it configurable and log a deprecation message?

In case anybody is interested in picking that up, some people implemented a resp3 parser: https://github.com/hverlin/redis/blob/main/src/parser/parser.v3.ts

I also ran into this issue because of a network policy. Maybe the status could be reported back onto the RedisFailover resource for better transparency. Currently the timeout is also...

I just run into this problem because i didn't read the docs. I assumed that there's an error instance as first argument.

It would be nice if we could infer the path based on the `--input-type`. My use case is that I want to use stdin or maybe add a new `--file-name`...

I just recently implemented an [openid connect filter for envoy](https://github.com/dgn/oidc-filter/blob/master/examples/envoy/envoy.yaml#L39-L52) that takes care of the handshake. Such a service could allow having the client secret central in the kubernetes cluster....

You'll need to install the `nanocomponent` module by yourself, instantiate it manually and use it in a view. We should create a follow-up issue to document that in choo or...