TheDiveO

Go doesn't support `fork()` in the way used by libtinynotify-systemwide, due to the way the Golang runtime works: it needs multiple Go routines which might map to multiple OS-level threads....

@cenkalti could you live with not breaking the API (not even on source level) but with adding the `New...WithOpts` siblings accepting options instead, similar to what was done with Docker's...

https://github.com/patrickmn/go-cache/blob/46f407853014144407b6c2ec7ccc76bf67958d93/cache.go#L1115

@harche thank you very much for this quick first response and offering to discuss it further, I highly appreciate this! Not surprisingly, we probably come from different use cases (which...

Revisiting the current draft, I notice that it currently can only report the demise of containers (https://github.com/harche/kubernetes/blob/d6cada8abc474551c461b3fc1fe41ac5356c522b/staging/src/k8s.io/cri-api/pkg/apis/runtime/v1/api.proto#L153), but not newly created or started containers. In my use cases I need...

my limited understanding is that gRPC provides the "streams" for the results, separately. So the server has open long-running responses and thus needs to handle filtering itself, according to each...

Is there a comparably simple way I could test drive your changes on a local development system, with a simple cri-o binary?

thank you very much for the pointer!

/activity ;)

@sy-records I appreciate your suggestion, but this is difficult to keep consistent in larger documents and lacks the chance of proper CSS styling (unless you add in convoluted HTML interspersed...