Mike Baum

@Petikoch Sorry for the delay, I must admit I missed your email. Well the issues I was experiencing was that whenever one BehaviourSubject emits an error the subscription to a...

Hi, we (Coveo) have implemented this feature in our own fork and would be willing to add a PR here. Let me know if you guys are interested.

> > Hi, we (Coveo) have implemented this feature in our own fork and would be willing to add a PR here. Let me know if you guys are interested....

+1 for this feature. Currently our application uses both Lambdas and Containerized microservices. I have been searching for a framework that would allow service discovery across both these types of...

@eddieburns55 Just wanted to check, it's been a while since I posted this issue, do you have any opinion on my questions?

@eddieburns55 Yeah, I also have the feeling that RxJava should be lightweight. Of my previous suggestions the only one in my mind that might be suitable for that library would...

@akarnokd > There seems to be nothing stopping this project to target Java 8 (although I don't remember what additions were made to the Swing API relative to 6) I'm...

@dims12 This was a pattern that was established before I joined the project. I guess the rational was to prevent people from instantiating the utils classes. I'm curious which classes...

@mfamador Awesome, in terms of the design would you be okay with adding the properties to the root schema? Something like this: ``` type PipelineSpec struct { Config *apiextensionsv1.JSON `json:"config,omitempty"`...

Sounds good to me. Some of these properties will come from varying levels of the `DeploymentSpec` schema, I feel like flattening the property path makes sense, but I fear a...