Glib Smaga

Hi @oakad, thanks for getting in touch. It took me a little bit to digest this issue and understand what is the actual problem you are trying to solve. Configuration...

Wouldn't that be a breaking change? While it's an easy work-around ("just wrap your functions"), it's still something that when pulled would case a build failure. I'm not sure we'd...

Interesting idea. @shaikatz are you able to provide a higher res image if it's not confidential? It's hard to see where the lines are pointing to.

Good find. `foo: "yes"` does the right thing, but it should work with `foo: yes` correctly as well. The underlying yaml library does the right thing, which likely means a...

It looks like at the core is the way yaml library handles `interaface{}` unmarshaling. Here is the smallest repro scenario for this bug: ```go package main import ( "fmt" "log"...

@tormoder Apologies for a long turn-around. This seems to have slipped under the cracks. It's not entirely clear what you are trying to do since you're doing overrides in the...

Linked code looked like something I wrote a while back, so I went digging. Found the original PR https://github.com/uber-go/fx/pull/384 Can't quite remember the reason why `${NOTSET:}` is treated explicitly as...

@seaunderwater is this reproducible without `hubble-relay` as well? By using the CLI directly on a particular node

Closing as stale (not sure why a bot haven't gotten to it yet). Please re-open if still relevant :]

> These seem to be both derived from the error in the hubble server side around attempting to list more flows than the current ringbuffer contents You are allowed to...